CSS Parser's shape doesn't allow the CSS property to be defined more than once.
Yeah, this is something we don't support currently, but I think it might be nice to handle also those cases.
Read full answer below βQuestion
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
Any
Reproducible demo link
https://grapesjs.com/demo.html
Describe the bug
The bug is related to ParserCss.js.
https://github.com/artf/grapesjs/blob/dev/src/parser/model/ParserCss.js#L7-L8
The parser expects the results to be stored in an array of a hash object containing a select string and a style hash object (and other media query arguments).
Example Result:
[
{
selects: "div, a, .a.b.c", //some selector with comma separtator.
style: {
background-image: url(img/gradient.png);
}
}
]
This prevents CSS from having the same property defined more than once and this is needed for better backward compatibility. The CSS is valid, but the editor will not be able to output the correct HTML.
Example CSS
div, a, a.b.c {
background-image: url(img/gradient.png);
background-image: -webkit-linear-gradient(to bottom, #dddddd, #aaaaaa);
background-image: -moz-linear-gradient(to bottom, #dddddd, #aaaaaa);
background-image: linear-gradient(to bottom, #dddddd, #aaaaaa);
}
Step to Reproduce in Demo:
Drop a custom block Insert
<div style=" background-image: url(img/gradient.png);
background-image: -webkit-linear-gradient(to bottom, #dddddd, #aaaaaa);
background-image: -moz-linear-gradient(to bottom, #dddddd, #aaaaaa);
background-image: linear-gradient(to bottom, #dddddd, #aaaaaa);">
hello
</div>
Export to HTML
Expected Behavior: All the CSS styling should be available in the HTML in the correct order
Current Behavior:
Only one of the background-image is exported.
https://user-images.githubusercontent.com/5863227/178131872-13726a77-5264-4d2a-9131-ed1e205387a2.mp4
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (2)
Yeah, this is something we don't support currently, but I think it might be nice to handle also those cases.
Thanks for reporting this, @Singwai.
The issue with CSS Parser's shape doesn't allow the CSS property to be defined more than once. appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.
What to try:
- Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
// your operation here
}, 0);
-
Check initialization order β make sure components are fully loaded before you interact with them
-
Use the editor's event system β listen to completion events:
editor.on('component:mount', (component) => {
// safe to interact with component here
});
Recommended next steps:
- Test with the latest GrapesJS version if you haven't
- Provide a minimal reproducible example (CodeSandbox) β this helps the team identify the root cause faster
- Include GrapesJS version, browser, and console errors in your report
Related Questions and Answers
Continue research with similar issue discussions.
Issue #4512
almost all examples from this page fail with grapejs
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Version 103.0.5060.134 (Official Build) Bu...
Issue #5525
Performance issue when adding more than 20 classes to a single component
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Edge v119.0.2151.72 Reproducible demo link...
Issue #4059
selector escape function doesn't support tailwindcss classes
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v97Describe the bug At line https://g...
Issue #4503
Missing inline styles used by CKEditor when adding raw html components
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chromium v96 Reproducible demo link https:...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins βPremium plugins ship with support, regular updates, and production-ready features β save days of integration work.
Browse premium plugins βBrowse Plugin Categories
Jump directly to plugin category pages on the marketplace.