Invisible webcomponents

Posted a workaround here https://github.com/artf/grapesjs/issues/3693

Hey @sriya-srinivasan can you create a reproducible demo, please?

@sriya-srinivasan any update please?

Thanks for reporting this, @sriya-srinivasan.

The issue with Invisible webcomponents 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);

2. Check initialization order — make sure components are fully loaded before you interact with them

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