You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 1, 2018. It is now read-only.
When using tappy on links, long-pressing a link in Safari/iOS opens the context menu - as soon as the finger is lifted off the screen, the link is followed, despite the context menu still being open.
Arguably, this smells like a bug in iOS - testing the event flow using http://patrickhlauke.github.io/touch/tests/event-listener_link.html it seems that when context menu is shown, Safari/iOS doesn't consistently fire touchcancel; in fact, if you keep the finger pressed, you can actually still scroll the page underneath the context menu and it fires touchmove events, and sometimes it then fires touchend if you lift the finger while the context menu is shown. Not sure if this is something that can be caught/prevented by tappy though...
The text was updated successfully, but these errors were encountered:
As I don't think there's realistically anything that can be done at tappy's end to consistently work around this iOS bug, I'm closing this (in the hope that Apple fix this at source instead)
When using tappy on links, long-pressing a link in Safari/iOS opens the context menu - as soon as the finger is lifted off the screen, the link is followed, despite the context menu still being open.
See https://www.youtube.com/watch?v=P_YJe1MQ4m8
Arguably, this smells like a bug in iOS - testing the event flow using http://patrickhlauke.github.io/touch/tests/event-listener_link.html it seems that when context menu is shown, Safari/iOS doesn't consistently fire
touchcancel
; in fact, if you keep the finger pressed, you can actually still scroll the page underneath the context menu and it firestouchmove
events, and sometimes it then firestouchend
if you lift the finger while the context menu is shown. Not sure if this is something that can be caught/prevented by tappy though...The text was updated successfully, but these errors were encountered: