-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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(drag-drop): events fired multiple times for short drag sequences on touch devices #13135
fix(drag-drop): events fired multiple times for short drag sequences on touch devices #13135
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I finally got drag-drop enabled in Google, so back to not being merge-safe |
Hi @crisbeto! This PR has merge conflicts due to recent upstream merges. |
619794f
to
8f8bd6d
Compare
8f8bd6d
to
2b87abb
Compare
2b87abb
to
21690bc
Compare
…on touch devices Fixes the `started` and `ended` events being fired multiple times for short drag sequences on touch devices. The issue comes from the fact that we listen both for mouse and touch events, which means that we also pick up the fake events that are fired by mobile browsers. Fixes angular#13125.
21690bc
to
2cfca06
Compare
…on touch devices (#13135) Fixes the `started` and `ended` events being fired multiple times for short drag sequences on touch devices. The issue comes from the fact that we listen both for mouse and touch events, which means that we also pick up the fake events that are fired by mobile browsers. Fixes #13125.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Fixes the
started
andended
events being fired multiple times for short drag sequences on touch devices. The issue comes from the fact that we listen both for mouse and touch events, which means that we also pick up the fake events that are fired by mobile browsers.Fixes #13125.