Skip to content
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

Fix event target fallbacking to map after marker drag (fix #3971) #4010

Merged
merged 1 commit into from
Jan 8, 2016

Conversation

yohanboniface
Copy link
Member

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 checking draggableMoved 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 for draggableMoved, do you recall? :)

@mourner
Copy link
Member

mourner commented Nov 11, 2015

I don't recall :(

@IvanSanchez
Copy link
Member

@yohanboniface ev._simulated is about synthetic click events coming from very small touch-drags. In other words, a simulated click is a drag small enough to fire events.

@IvanSanchez
Copy link
Member

@yohanboniface Not the cleanest PR ever (I wouldn't expect less from a 'brainmelt' tag ;-) ) but looks good to me.

IvanSanchez added a commit that referenced this pull request Jan 8, 2016
Fix event target fallbacking to map after marker drag (fix #3971)
@IvanSanchez IvanSanchez merged commit 88fa86a into master Jan 8, 2016
@mourner mourner deleted the dragend-click branch January 8, 2016 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants