Style Manager is inaccurate when using combined CSS selectors which contains "bout" and componentFirst = true
@artf Awesome! Thank you. To use these updates, I guess I would just need to re-build the library locally with your changes until next release. I'll give that a shot.
Read full answer below βQuestion
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
Chrome 100
Reproducible demo link
https://jsfiddle.net/4fmd732c/3/
Describe the bug
How to reproduce the bug?
Given
a) componentFirst is set to true
b) An element has multiple classes
c) CSS rule uses combined selector of multiple classes
d) One of the classes contains the word "bout"
Then: Style Manager does not accurately display current styling
Navigate to linked JS Fiddle
- Select Div in editor
- In the Style Manager, expand "Decorations" and take note of background color
What is the expected behavior?
- Style manager should indicate background is green
What is the current behavior? Style manager indicates background is white
- If you change class name from ".bout" to ".out", it works fine
- If you change ComponentFirst to "false", ".bout" and ".out" work fine
If is necessary to execute some code in order to reproduce the bug, paste it here below:
// your code here
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (4)
@artf Awesome! Thank you. To use these updates, I guess I would just need to re-build the library locally with your changes until next release. I'll give that a shot.
Nice catch, thanks for the report @barryross
@artf when do you foresee the next release going out?
Thanks for reporting this, @barryross.
Great question about Style Manager is inaccurate when using combined CSS selectors which contains "bout" and componentFirst = true. The recommended approach with StyleManager is to use the event-driven API.
Start here:
- Check the GrapesJS documentation for your specific module
- Look for the
on()event listener method - Most operations can be achieved by listening to editor and component events
Common patterns:
// Listen for changes
editor.on('change', () => console.log('something changed'));
// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));
If you're still stuck:
- Share a minimal CodeSandbox reproduction
- Include what you've already tried
- Mention your GrapesJS version
- The community is here to help!
Related Questions and Answers
Continue research with similar issue discussions.
Issue #6458
sector.setName doesn't work
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://jsfi...
Issue #6706
TypeError: e.getRoot is not a function (Race condition in Style Manager)
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? All browsers (Chrome, Safari, Firefox, Edg...
Issue #5487
Style Manager doesn't display multiple rules for the same class
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox Reproducible demo link https://jsf...
Issue #5990
When you delete a component, duplicate classes between components will be deleted.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 126.0.6478.127(Windows) Reproducibl...
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.