-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Double tap on IOS 13 Public Beta doesn't work #1232
Comments
I can confirm that the linked pen does not work on iOS 13 (Dev Beta 8), but does work in iOS 12.4.1 Personally been having issues with Swipe on iOS 13 as demonstrated by the official swipe/pan example, which again, works in 12.4.1 but not 13. |
Double tap still doesn't work in new IOS 13.1 Public Beta. |
also 'panstart' event fires, but 'panend' never fires, instead almost instantly 'pancancel' fires .... this all also only on IOS13 beta |
The official swipe/pan example is still not working on iOS 13 final release 😕 |
In iOS 13, swipe will make the page slide, use the following code to make it work properly.
|
The issue with double-tapping appears to be across the board, not just with Hammer.js. Here is a pure JS example that has the same issue (this is not my jsfiddle, I found it while Googling the double tap issue) - |
The double tap issue isn't present anymore in the last Beta version ! |
There is no longer a swipe problem in ios 13.1. There is a problem with the iOS 13.0 system. |
To me it seems that the double tap problem has not been solved. On my iPad using iPadOS 13.1.3 the demo on https://codepen.io/choskim/pen/vezzwZ still does not work as expected. |
The double tap pen works for me on 13.2 (17B84, iPhone) |
Just to be clear: I am not using a pen. I don't know if this makes any difference. And an update to iPadOS 13.2 solved the problem for me, too. |
Double tap works perfectly fine on IOS 12 but doesn't work anymore on IOS 13 Public Beta.
The example from the README is the best way to see it :
https://codepen.io/choskim/pen/vezzwZ
The text was updated successfully, but these errors were encountered: