fix Safari drag&drop functionality when cancelling dragover event in parent element #458
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At least on Safari Windows, if you cancel the dragover event on any parent element of the droppable area (to prevent the browser from opening a file that was dropped outside of our designated area), then Safari completely ignores the drop action. (nothing happens at all)
This patch has been on our production code for at least 4 months so I would say it's quite safe for merging. Not sure if anyone should actually depend on this event bubbling up on the DOM, we don't use the built-in queue plugin so let me know if this patch is no good.