Issue #5905πŸ’¬ AnsweredOpened May 24, 2024by gladykov0 reactions

Unable to open component settings again, after clicking component and then clicking Blocks

Quick answerby artf

Thanks @gladykov but this is not related to the core, it's just an example behavior implemented in the demo.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Opera 10.0.5130.23 | Linux

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

  1. Clear canvas
  2. From Blocks menu add 1 Column component -> Settings tab is opened automatically :ok_hand:
  3. Click newly added component inside editor frame
  4. Go to Blocks tab
  5. Click component again

Expected: Settings opened again

Actual: Settings is not opened.

Note: I understand this works properly when component was not previously selected. Easy to verify this behavior by adding 2 components. But it introduces 2 different behaviors, depending on previous user action. I would expect that clicking component always opens Settings

Video:

https://github.com/GrapesJS/grapesjs/assets/24669884/1c652513-bc28-4226-a7c0-46fdd19d97a2

Code of Conduct

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

Answers (2)

artfβ€’ May 25, 2024

Thanks @gladykov but this is not related to the core, it's just an example behavior implemented in the demo.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @gladykov.

The issue with Unable to open component settings again, after clicking component and then clicking Blocks 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.