Issue #5720💬 AnsweredOpened March 6, 2024by bernesto0 reactions
questionbugcomponentsstyle-managertypescript

Propagating component defaults can break layers when child comments are introduced

Quick answerby artf

Good catch @bernesto

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v122

Reproducible demo link

https://jsfiddle.net/n38vbktg/

Describe the bug

How to reproduce the bug?

  1. Create a component that propagates defaults that include layerable = true.
  2. Introduce a comment under the competent.

What is the expected behavior? The comment either remains hidden, or does not cause an error.

What is the current behavior? The editor treats the comment as an HTMLElement. This triggers several errors when the editor tries to read non-existent properties from the node, such as getComputedStyle or getClientRects. Both methods should perform a check first. Or - a new type should be introduced for comments that overrides the defaults propagated from the parent.

Errors occur here: https://github.com/GrapesJS/grapesjs/blob/ac554a344653d750e9495af26edbf96fc3a9bf6f/src/commands/view/ShowOffset.ts#L39 and here: https://github.com/GrapesJS/grapesjs/blob/ac554a344653d750e9495af26edbf96fc3a9bf6f/src/utils/dom.ts#L40

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (2)

artf• March 7, 2024

Good catch @bernesto

ClaudeCode• May 17, 2026

Thanks for reporting this, @bernesto.

Great question about Propagating component defaults can break layers when child comments are introduced. 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.

Issue #4752

Component with pointer-events: 'all' (except wrapper) or editable component are draggable & droppable to itself.

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 107.0.5304.121 (Official Build) (arm6...

3 answersUpdated December 12, 2022

Issue #5424

`component:styleUpdate` event is not fired

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 116.0.5845.187Reproducible demo link...

2 answersUpdated October 10, 2023

Issue #4897

component:styleUpdate / component:styleUpdate:propertyName not fired

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Edge 109.0.1518.70 Reproducible demo link...

4 answersUpdated May 22, 2023

Issue #4792

Drag and drop broken in 20.2

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v108Reproducible demo link see belowD...

4 answersUpdated December 20, 2022

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 →

Related tutorials

In-depth guides on the same topic.

All tutorials →

Tutorial

Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live

We're shipping a set of discovery upgrades. New label filters, a proper compatibility switch for GrapesJS vs Studio, one-click and a smarter sort bar.

Tutorial

GrapesJS vs Webflow vs Tilda: What to Choose for Your Business in 2026

Choosing the right website platform in 2026 is no longer just about building a site

Tutorial

GJS Market 2.0 - Donations, Tracking, Labels and Better Product Discovery

We’ve rolled out a new set of GrapesJS marketplace updates across GJS Market, focused on improving how creators distribute products

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.

PresetsPluginsComponentsBlocksAssetsCommandsI18nLayersStylesStoragesRTENewslettersWeb pagesSite builders