Issue #3291✓ SolvedOpened February 25, 2021by marcepoblet4 reactions

BUG (v0.16.41): the duplicate icon from the icon toolbar is modifying the original element too

快速解答by artf3

Thanks for the report guys, I'm aware of the bug and it's already fixed in dev. I've just totally forgot to release it 😬 I'll try to release it today

Read full answer below ↓

Question

Version: v0.16.41

Are you able to reproduce the bug from the demo?

[ ] Yes

What is the expected behavior? The elements duplicated not should be impact the changes in the original element.

Describe the bug detailed steps:

  • select an element (text, image, etc)
  • click on the duplicate icon from the toolbar
  • modify the new element duplicated
  • the original element is modified too

https://user-images.githubusercontent.com/64096863/109187944-27f04680-7771-11eb-8ba4-1181ed56b08f.mp4

What is the current behavior? when some elements are duplicated, and the element duplicated is modified, the original element is modified too.

Are you able to attach screenshots, screencasts or a live demo?

[ ] Yes (attached a video)

Answers (4)

👍 Most helpfulartfMarch 2, 2021

Thanks for the report guys, I'm aware of the bug and it's already fixed in dev. I've just totally forgot to release it 😬 I'll try to release it today

devtechkMarch 4, 2021

@artf Thanks a lot! you saved me a lot of work _ I was trying to debug this issue all this entire afternoon... then for casuality I've realized, checking npm that the 0.16.44 version was out...

You saved man. Thank a lot! Donation, you deserve it all! ❤️

aadilmehrajbhatMarch 1, 2021

Regression issue since "grapesjs": "0.16.34"

ClaudeCodeMay 17, 2026

Thanks for reporting this, @marcepoblet.

The issue with BUG (v0.16.41): the duplicate icon from the icon toolbar is modifying the original element too 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.