IOS browsers have a 300ms click delay - But developers can bypass it | Hacker News


Article asserts it's there to detect double taps, but I'd add that it's a very useful user experience tweak to help deal with mis-taps. On HN, for example, I'll frequently hit the article link instead of the comments and this delay (combined with the network latency) often lets me re-tap the right link.



 
 

Related Links:

Content

Cached Text (at the time of saving)


Article asserts it's there to detect double taps, but I'd add that it's a very useful user experience tweak to help deal with mis-taps.
On HN, for example, I'll frequently hit the article link instead of the comments and this delay (combined with the network latency) often lets me re-tap the right link.
reply
> Of course, that only works if you are on an iOS device.
It also works in Chrome Beta for Android.
reply
Excellent, I did not test that yet. I mostly meant to say that you cannot see the delay if you are browsing on a non-touch device (because there is no delay).
reply
One of the developers of FastClick.js here. We made this thing because we thought that the problem deserved a thin compatibility layer as a solution, rather than forcing developers to rewrite their code to use a different kind of button all over the place (then rewriting it again when the devices change their behaviour).
The code is in production use on the FT web app, which is deployed across iOS devices, Android (both Chrome and the Android browser), Firefox (in test), Blackberry (both Playbook and phone) and Windows (IE10). We've fixed a bunch of bugs since the initial release and we should be putting the new code on GitHub in a few days (http://github.com/ftlabs).
Feel free to post questions about FastClick on Stackoverflow if you have any problems... I'm monitoring it for mentions of FastClick and will answer most of the time.
reply
Great library, going to give it a shot in one of my upcoming projects.
Quick question - I just tried the demo on IE on a Nokia Lumia 710 running WP 7.5 Mango, and there was no difference between A and B. Do you have any idea why FastClick might not work on Mango?
reply
Yeah, but it's still less annoying than seeing MAC used for Apple's desktop and notebook line.
reply
This is already well known, and the case with most browsers on touch devices.
So terrible title, useful article.
reply
Why is it a terrible title? I personally didn't know about the 300ms delay, and the title seemed to describe the article perfectly.
reply
Because the title is "IOS browsers have a 300ms click delay", when in fact it affects a lot of mobile platforms (BB, iOS, WP7, some older Android versions), not just iOS. The article itself doesn't even mention iOS or iPhone.
reply
Also, avoid doing as much work as you can inside event handlers.
reply
Is there a JS fiddle somewhere where you can see the difference?
reply
You may know this already, but running this test on Android ICS (stock browser) and B can't be selected.
edithttp://bit.ly/L2JatN Short url for easy mobile typing
reply