fix(SwipeRecognizer): related to Issue #815 #948
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
added 3 commits
March 20, 2016 09:19
|
Oh nvm found it, Chrome Canary for some reason doesn't have ev.srcEvent.toElement. |
nkarczmarzyk
approved these changes
Oct 14, 2021
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.
Hey @thejae, yeah I think you're right. I believe your Issue #945 is related to #815 and #942 since Pan and Swipe gestures are somewhat similar. For now though, you can get around it with this.
Cache the the first
srcEventin theSwipeRecognizerand retrieve it during emit. Also, I'm not sure about you mean aboutev.srcEvent.toElementsince I can't find that property.