-
Notifications
You must be signed in to change notification settings - Fork 23
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
Is hammertime still necessary in modern mobile browsers? #74
Comments
YMMV is the honest truth - https://bugs.webkit.org/show_bug.cgi?id=150604 I wish i had a better answer than 'it depends' but i don't. Apple does what it wants, based on heuristics, w/o even telling which of their webviews or ios versions webkit bugs are applied to. worth noting though is that hammertime is very simple, it just adds an linline touch-action: manipulation style to interactive elements. Changing this from a developer perspective is much easier on a case by case basis than the timer based approach that ftlabs/fastclick uses. happy hacking :) |
lol its u robert - here, more links: 2013 they said, yay, its fixed: 2018: unresolved bug remains anywho |
I admit I know nothing about the subject, but do we still need to be using this or is support for removing click delays on taps just built in these days? This SO post seems to indicate it's all built in https://stackoverflow.com/questions/42250283/is-fastclick-js-still-needed as does this ftlabs/fastclick#514 @runspired @eriktrom
The text was updated successfully, but these errors were encountered: