Issue #4812πŸ’¬ AnsweredOpened December 27, 2022by FaisalShaikhHA1 reactions

Layerable property not working as expected in parent-child scenario.

Quick answerby artf❀ 1

Unfortunately this is how layerable currently works so it's not a bug, but I'd be glad to accept a PR to improve this behaviour.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

107.0.5304.110 (Official Build) (arm64)

Reproducible demo link

https://codepen.io/faisal-praella/pen/rNvOwgR

Describe the bug

When the parent component is set to layerable: false it is not visible & all its child not visible in the layer manager. When one of its child components is set to layerable: true it should be visible in the layer manager.

What is the expected behavior? The parent component should be hidden along with its children but the child with layerable: true should be visible in the layer manager.

What is the current behavior? The child with layerable: true is not visible in the layer manager.

<section data-gjs-layerable='false'>
    <div>Bar Foo</div>
    <h2 data-gjs-layerable='true'>Lorem ipsum</h2> // not visible in layer manager
    <p>Foo bar</p>
<section>

Code of Conduct

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

Answers (2)

artfβ€’ January 2, 2023

Unfortunately this is how layerable currently works so it's not a bug, but I'd be glad to accept a PR to improve this behaviour.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @FaisalShaikhHA.

The issue with Layerable property not working as expected in parent-child scenario. 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:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order β€” make sure components are fully loaded before you interact with them

  2. 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.

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 β†’

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.