3 ms·
It removes the 300ms delay while the browser waits for a double-tap (to make sure you really meant to click on that link and not zoom in), which is supposed to
by 0942v8653 12y ago
It removes the 300ms delay while the browser waits for a double-tap (to make sure you really meant to click on that link and not zoom in), which is supposed to be a huge UX improvement.
- harlanlewis 12y agoNote that Android no longer applies the 300ms delay regardless of viewport scalability. http://updates.html5rocks.com/2013/12/300ms-tap-delay-gone-away http://updates.html5rocks.com/2013/12/300ms-tap-delay-gone-a... There are a number of plugins to remove the 300ms delay from other touch browsers. Here's one: https://github.com/ftlabs/fastclick https://github.com/ftlabs/fastclick
- jordanlev 12y agoFascinating... I never heard about this side-effect of disabling zoom! I did some googling and from what I can tell, this only applies to some Android browsers, not iOS? If that's the case, it seems like throwing out the baby with the bathwater, since it does have the accessibility issue and removing the delay can be better-achieved on ALL devices with some of the JS libraries that others have linked to. Here's a blog post I found that talks about the limitations of this "avoid touch delay by disabling zoom" technique: http://timkadlec.com/2013/11/Avoiding-the-300ms-click-delay-accessibly/ http://timkadlec.com/2013/11/Avoiding-the-300ms-click-delay-...