Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certain WYSIWYG classes/options missing in front-end #4603

Open
LaurensBurger opened this issue Aug 16, 2024 · 5 comments
Open

Certain WYSIWYG classes/options missing in front-end #4603

LaurensBurger opened this issue Aug 16, 2024 · 5 comments

Comments

@LaurensBurger
Copy link
Collaborator

LaurensBurger commented Aug 16, 2024

Product versie / Product version

2.6.13 - latest

Customer reference

lv 184

Omschrijf het probleem / Describe the bug

Examples are blockquotes, and text size: settings these either has no visible impact in the front-end or defaults to "user agent stylesheet"
image
image
Where "text-big" does not exist in the style sheets.

Shouldn't these exist in the style sheet by default since they are available in the editor?

@LaurensBurger LaurensBurger added bug triage Issue needs to be validated. Remove this label if the issue considered valid. labels Aug 16, 2024
@sergei-maertens
Copy link
Member

In short: no - we don't use the WYSIWYG editor stylesheets at all since they conflict too much. Most of the styles in these editors are done via inline-styles, this .text-big class is new to me.

Which editor is this - the formio WYSIWYG, or our own in the admin interface?

@LaurensBurger
Copy link
Collaborator Author

From our own admin interface.

@sergei-maertens
Copy link
Member

Refinement: could be related to the TinyMCE upgrade, perhaps some inline styles have been replaced with class names? We need to check/confirm this, and check if we deliberately allow(ed) the blockquote content element.

If this should be supported, we need to update the CSS in the SDK to make sure it is displayed properly. NL DS components/styles may be relevant here, but let's keep it simple if possible.

@sergei-maertens sergei-maertens removed the triage Issue needs to be validated. Remove this label if the issue considered valid. label Aug 19, 2024
@sergei-maertens
Copy link
Member

@LaurensBurger how important is this, what's the prio?

@LaurensBurger
Copy link
Collaborator Author

@sergei-maertens low. Workaround(s) available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants