Issue #3463πŸ’¬ AnsweredOpened May 18, 2021by anatoli-dp1 reactions

Inspector overflow broken

Quick answerby anatoli-dp❀ 1

Maybe put the controls in the front of the text and then offset the entire box slightly for each indent or stacked item. That way u can stack them as far as you want without issue 🀷 Im going to end up rolling my own solution to achieve that but since I don't understand the structure of how ur code is done I'm not gon...

Read full answer below ↓

Question

WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.mdDo a quick SEARCH first, to see if someone else didn't open the same issueAll relative statements/questions have to be filled/answered, otherwise, the issue might be CLOSEDJSFiddle Starter template https://jsfiddle.net/szLp8h4nCodeSandbox Starter template https://codesandbox.io/s/1r0w2pk1vl Version: You can get the version by typing grapesjs.version into the console Are you able to reproduce the bug from the demo?[ x] Yes[ ]...

Answers (4)

anatoli-dpβ€’ May 22, 2021

Maybe put the controls in the front of the text and then offset the entire box slightly for each indent or stacked item. That way u can stack them as far as you want without issue 🀷 Im going to end up rolling my own solution to achieve that but since I don't understand the structure of how ur code...

artfβ€’ May 22, 2021

Yeah, unfortunately, the default layer panel is not that scalable, we need to rethink how is rendered

artfβ€’ May 22, 2021

Yeah moving controls in front of the text sound reasonable (eg. and make them visible only when I hover the component). Anyway, being not such a common case having so much messy structure I wouldn't put a lot of priority on this problem, but for sure it would cool to fix such a limitation. If anyon...

GJSBlockβ€’ May 17, 2026

Thanks for reporting this, @anatoli-dp. The issue with inspector overflow broken 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 wra...

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.