Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Double Entry in Layers if Component is moved directly after add #5820

Closed
2 tasks done
rhoenerSBS opened this issue Apr 17, 2024 · 1 comment
Closed
2 tasks done

Comments

@rhoenerSBS
Copy link

rhoenerSBS commented Apr 17, 2024

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v123

Reproducible 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?

  1. Open Fiddle
  2. Drop component into canvas at the last position (does not happen here)
  3. Drop another component into canvas at the last position (from now on the dropped components get two entries in the layers panel)

What is the expected behavior?
Component can be moved and still have only one entry in the layer panel.

What is the current behavior?
The moved components have 2 corresponding entries in the layer panel.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@rhoenerSBS
Copy link
Author

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.

@artf artf closed this as completed in 1085831 May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant