Double Entry in Layers if Component is moved directly after add
I initially wanted to realize the same behavior with a function in the droppable property of the parent component to prevent components being dropped at a specific index but unfortunately the index is not given as a param for that function.
Read full answer below βQuestion
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v123Reproducible demo link https://jsfiddle.net/xwgons8z/Describe the bug I'm trying to programmatically move an added component to a specific position in the parent since I have child components, that are supposed to stay at the last index, but there is a bug in the layers that once the component is moved it has two corresponding entries in the layers panel. How to reproduce the bug?Open FiddleDrop component into canvas at the last position (does not happen here)Drop another component into c...
Answers (2)
I initially wanted to realize the same behavior with a function in the droppable property of the parent component to prevent components being dropped at a specific index but unfortunately the index is not given as a param for that function.
Thank you for reporting this issue. You've identified a subtle timing bug in GrapesJS related to how the Layers panel updates when a component is programmatically moved immediately after being added. Root Cause The issue stems from a timing conflict between the component:add event and the subsequen...
Related Questions and Answers
Continue research with similar issue discussions.
Issue #5305
"component:add" event triggers when components are moved
GrapesJS version 0.21.4[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 113.0.5672.63 Reproduc...
Issue #5379
Class modifications of components are not automatically detected
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 116Reproducible demo link htt...
Issue #4255
The initial toolbar move button does not get removed if you set the draggable prop to false programmatically
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v98.0.4758.80Reproducible demo link h...
Issue #6409
Cannot drag to move components on mobile
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v133 Reproducible demo link https:/...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins β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.
Tutorial
UnStudio for GrapesJS: 4 Plugins to Build Better Visual Editors
Meet UnStudio, a new GrapesJS plugin studio with four tools, safer and better editor: Command Palette, Responsive Pack, Autosave & Restore, and Autofill
Tutorial
Messaging on gjs.market: talk to a studio before you buy, not after
We've launched private messaging between buyers and studios. One thread per buyerβstudio pair, the whole history in one place.
Tutorial
GrapesJS DevTools: A Developer Panel Inside Your Editor
If you've ever debugged GrapesJS with console.log(editor.getSelected()) and a dozen throwaway event listeners β this post is for you.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.