fix isOver on nested drop targets (fix #13) #29
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.
Current behavior :
- find all the drop targets that are under the mouse
Fixed behavior :
- take the first element under the mouse
- find any drop targets that are either this element or one of its parents
- sort them by their position in the DOM (from deep to shallow)
Here is a codesandbox to see the different behavior between html5 and mouse backends (to change the backend, see index.js).