-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
dragover event cancelling #210
Comments
Did you have a chance to take a look at this? |
I do not understand what you want from me? Sortable fully captures drag-events and processes them. |
The dragover event handler on the document never gets called because Sortable is not allowing the event to bubble. I need to implement my own scroll handler, so I need to be able to catch that event. If I comment out the code in Sortable that I highlighted in my first comment on this issue, then I am able to handle the event directly. However, I don't know if there is a reason the event is prevented from bubbling. If so, I was hoping Sortable could expose another event to make it possible to write a custom scroll handler. Thanks, Chris |
Alas, if I remove But possible to add options: eventBubbles: {
dragover: boolean,
drop: boolean
} |
That would be great! |
Try
|
I tested it out and it does what I need. Thanks! |
Good. |
Do you have any plans for releasing this change? |
Yes, changes already in the dev-branch. |
I have a really strange setup and the built-in scrolling in Sortable doesn't work for me (it's a case far outside of what you'd want to support).
I was going to implement my own scroll handler, sort of similar to the built-in one, but noticed that the dragover event is getting cancelled: https://github.com/RubaXa/Sortable/blob/26f148ce4456fd21e5c149c1c5d637ebc116034f/Sortable.js#L461
I am wondering if that has to get cancelled there. And if so, would you consider exposing an event or something in Sortable I could hook into as an alternative.
Thanks,
Chris
The text was updated successfully, but these errors were encountered: