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
Crashing in isOver with empty targetId #1245
Comments
Same issue |
I tried to revert this change 0feb250#diff-ac418ba19283aec1fb0b70e6570c5613 and resolved.. . |
Same issue. |
Confirmed we are receiving the same issue - Reverting to 7.0.2 fixes the issue |
This is being caused because the change at 0feb250 is allowing target ID to be Currently it's prototype is:
unlike the other functions which changed in that pr which move
and check:
A fix for this issue will be to check for |
This should be fixed by cfrank's PR in a release today |
Amazing, guys, thanks @cfrank |
Describe the bug
I have a connected drop target that is removed from the DOM, once something is dropped on to it.
Now since upgrading to
v7.1.0
, I'm gettingin the
monitor.isOver()
call inside thecollect
function.Somehow, it sees that the collect function is still called one more time, after the drop target has been removed (
targetId
is undefined).Interesting
6.0.0
resolved the issue.setTimeout
wrapper around my callback that removed the drop target, resolved the issue.Any idea what could cause that?
To Reproduce
Steps to reproduce the behavior:
monitor.isOver()
incollect
drop(...)
that removes the drop targetExpected behavior
There is no timing issue with
isOver
and drop targets can be immediately removed.Screenshots
Desktop (please complete the following information):
7.1.0
The text was updated successfully, but these errors were encountered: