Issue #6365šŸ’¬ AnsweredOpened January 8, 2025by MLMarxx0 reactions

Style Manager Fails to Interpret Descendant Selectors Correctly

Quick answerby artf

Yeah, that's not supported as there might be some performance implications trying to match any possible rule there. What you can do though is select any rule via styleManager.select

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome Version 131.0.6778.205

Reproducible demo link

https://codesandbox.io/p/sandbox/naughty-microservice-5hp3h4

Describe the bug

How to reproduce the bug:

  1. Add the dark-style class to the body:
    editor.getWrapper().addClass("dark-style");
    
  2. Add a descendant selector rule:
    editor.CssComposer.addRules(".dark-style .test-block { margin-top: 50px; }");
    

What is the expected behavior: Interpret in style manager as margin-top: 50px;

What is the current behavior: Does not show up in style manager, but renders correctly in canvas

Html example:

<div id="gjs">
  <div class="test-block">Hello World!!!</div>
</div>

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Answers (4)

artf• January 10, 2025

Yeah, that's not supported as there might be some performance implications trying to match any possible rule there. What you can do though is select any rule via styleManager.select

MLMarxx• January 10, 2025

Ok, thanks for clarification - currently using select, any ideas how to target media tags that way?

artf• January 11, 2025

You can get the CSSRule you need (getRule) and then pass it to styleManager.select

ClaudeCode• May 17, 2026

Thanks for reporting this, @MLMarxx.

Great question about Style Manager Fails to Interpret Descendant Selectors Correctly. The recommended approach with StyleManager is to use the event-driven API.

Start here:

  1. Check the GrapesJS documentation for your specific module
  2. Look for the on() event listener method
  3. 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.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

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.