[BUG] Generated styles do not escape colons in classnames
Question
Currently using GrapeJS for a project that I am working on locally and integrated it with some tailwind UI components.
It mostly works great, but I have noticed that making changes on some elements does not work (for example, changing text color or formatting).
Looking at it further I can see that this is because the generated styles do not escape colons from the classes grapesJs uses to make the CSS selector.
For example, this is a selector grapeJs outputs:
.text-3xl.leading-9.font-extrabold.text-gray-900.sm:text-4xl.sm:leading-10.lg:text-5xl.lg:leading-none{
color:#3866c2;
}
The selector should actually be something like this:
.text-3xl.leading-9.font-extrabold.text-gray-900.sm\:text-4xl.sm\:leading-10.lg\:text-5xl.lg\:leading-none{
color:#3866c2;
}
Answers (1)
Thanks for the report @kierenayima Selectors will be escaped in the CSS in the next release
Related Questions and Answers
Continue research with similar issue discussions.
Issue #1909
SetComponents is sometimes very slow
Hi all We're working on a newsletter app and are using grapesjs as the email editor with the newsletter preset plguin and some custom chang...
Issue #2419
[BUG] Absolute dragmode does not work on touch devices
Absolute dragmode (with grapesjs touch plugin) does not work on touch devices. GrapesJS version:0.15.8 Expected behavior: The user should b...
Issue #1567
rte toolbar bug
Hello all, I am using the latest grapesjs stable version (40) and I noticed the following bug in the rich text editor: If the user drags an...
Issue #1585
Hiding text editor
Your method "hideToolbar " does not provide for a situation where the text editor is greater than 100px. As a result, its piece is visible...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.