Patch TouchBackend to solve e.targetTouches bug in iOS 13 #1631
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
|
Thanks for the PR! Have you verified that this fix works on an iOS device? |
|
Yes, I've tried it locally in my project with an iPad running iOS 13.2.3. It does seem working properly. |
darthtrevino
approved these changes
Dec 2, 2019
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.
Based on the discussions and findings over #1585, I believe Safari in iOS 13 can somehow lose
e.targetTouchesafter a few renders.As a workaround I set up a private property in
TouchBackendto “cache” a valid targetTouchfromtouchstartevent, then use it as a fallback intouchmoveevent handlers when it fails to get client offset from an emptye.targetToucheslist.And this should fix #1585.