Issue #5484πŸ’¬ AnsweredOpened October 26, 2023by pittleCheung0 reactions

Clone tabs and clone tab is not right now

Quick answerby artf

Please, open bug issues only if related to the core library, not plugins.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

latest version of Chrome

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

https://github.com/GrapesJS/components-tabs question one

Code SnippetHTML
<img width="1421" alt="image" src="https://github.com/GrapesJS/grapesjs/assets/114127651/a3afe6c7-d644-40f0-97e5-cc3e3c595939">

click the tab clone , the tab four is be cloned , look the below img

<img width="1425" alt="image" src="https://github.com/GrapesJS/grapesjs/assets/114127651/90db58ba-ba7a-404a-8061-a7f232d5e400">


question two
<img width="1434" alt="image" src="https://github.com/GrapesJS/grapesjs/assets/114127651/0cfd4d79-0866-4ad3-88ff-eb41b0b85576">

click the tabs clone, The picture after cloning is as follows
<img width="1424" alt="image" src="https://github.com/GrapesJS/grapesjs/assets/114127651/a0f2f3e7-6e0a-403b-b09a-209447b0821c">

 The contents of the tab are not clone


### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Answers (2)

artfβ€’ November 1, 2023

Please, open bug issues only if related to the core library, not plugins.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @pittleCheung.

The issue with clone tabs and clone tab is not right now 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.