Checklist: fix duplicate trigger on Chrome Mobile #2032
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @jhchen, I believe this is a straightforward fix for this issue. Let me know if you want me to change anything. Thanks. |
gildo
approved these changes
Jul 4, 2019
|
This looks like it's been fixed in the develop branch |
It hasn't fixed in the develop branch @jhchen . Can you fix this :D |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #2031
Both
mousedownandtouchstartare being triggered on Chrome Mobile. We can prevent themousedownevent from triggering on touch devices by callinge.preventDefault()on thetouchstartevent. Citing MDN:More details at #2031 and #759 (comment)
cc @patleeman