fix: only call onDoubleClick for the dblclick event and not for the detected doubleTab in onTouchPanningStart #484
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
…etected doubleTab in onTouchPanningStart
|
Thanks! 🚀 |
|
🎉 This PR is included in version 3.6.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
The Pull Requests addresses the issue: #453
The problem is that the
onDoubleClickfunction is fired twice, once by the correctdblClickand the second time by thetouchstartevent.onTouchPanningStarthas its own implementation to detect if it was a double tap or not, and if it was, it fired theonDoubleClickfunction. I think the call toonDoubleClickis no longer needed and can be removed in favor of thedbClickevent.I tested the implementation on the following devices: