Fix event target fallbacking to map after marker drag (fix #3971) #4010
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.
Fix #3971
Given that the dragged marker was not listening to click events,
_findEventTargets
was using current map instance as default (which is the normal behaviour) target, but then in_fireDOMEvent
we were not checkingdraggableMoved
with the real event target.@mourner
e._simulated
comes from f9ea475, but I don't get why we needed and still need it when checking fordraggableMoved
, do you recall? :)