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
"dragstart" and "dragend" Events Not created for sidebar elements #2627
Labels
Comments
Same issue here, any workaround / fix? |
Not yet. |
v10 doesn't use drag event anymore (many problem, specially on Safari) so I re-did with raw mouse (and touch) events. What you are asking is for GS to generate synthetic 'dragstart' event. currently only the grid does that, side widgets do not. feature request. if you want to donate this could probably be added. |
adumesny
changed the title
"dragstart" and "dragend" Events Not Working with grid-stack-item class
"dragstart" and "dragend" Events Not created for sidebar elements
Mar 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Subject
When using Gridstack v10.1.1 with React, implementing the drag and drop feature using the .grid-stack-item class seems to override and break the dragstart and dragend events on div elements from being dragged and dropped into the grid.
Drag and drop works fine, but I need to listen to the drag state from the elements being dragged from the sidebar.
Environment
Steps to reproduce
For reference : https://jsfiddle.net/axwh8odu/14/
Expected behavior
The dragstart and dragend events should fire when starting and ending the drag, allowing for custom behavior during these events.
Actual behavior
The dragstart and dragend events do not fire when dragging elements with the grid-stack-item class from the sidebar, preventing any custom drag behavior from being implemented.
I am looking for any workarounds or fixes that might allow the dragstart and dragend events to work as expected with Gridstack items. Additionally, insights into why these events are being overridden or suggestions on how to prevent this issue would be greatly appreciated.
Thank you for your assistance and the work you put into maintaining Gridstack. It's an invaluable tool for our project, and I look forward to any guidance you can provide on this issue.
The text was updated successfully, but these errors were encountered: