IOS browsers have a 300ms click delay - But developers can bypass it
developers.google.com
IOS browsers have a 300ms click delay - But developers can bypass it
1–10 of 58 posts
Re: IOS browsers have a 300ms click delay - But developers can bypass it
#2This article was from 2011 (EDIT: oops, I said 2010 but the article says "January 2011" - though I'm sure they had it out before then) - I think everyone who's done iphone web dev is either using this, or has come up with something similar.
The HTML5 Mobile Boilerplate project uses "Fast Buttons": https://github.com/h5bp/mobile-boilerplate/wiki/JavaScript-H...
Re: IOS browsers have a 300ms click delay - But developers can bypass it
#3This is already well known, and the case with most browsers on touch devices.
So terrible title, useful article.
Re: IOS browsers have a 300ms click delay - But developers can bypass it
#4Also, avoid doing as much work as you can inside event handlers.
Re: IOS browsers have a 300ms click delay - But developers can bypass it
#5This is already well known, and the case with most browsers on touch devices. So terrible title, useful article.
Why is it a terrible title? I personally didn't know about the 300ms delay, and the title seemed to describe the article perfectly.
Re: IOS browsers have a 300ms click delay - But developers can bypass it
#6Is there a JS fiddle somewhere where you can see the difference?
Re: IOS browsers have a 300ms click delay - But developers can bypass it
#7This is already well known, and the case with most browsers on touch devices. So terrible title, useful article.
Why is it a terrible title? I personally didn't know about the 300ms delay, and the title seemed to describe the article perfectly.
Note that Google doesn't mention iOS or Apple anywhere in the article, yet the submission is "iOS has a 300 ms delay". It's in Android webview, too, not just iOS (probably it's something in WebKit?)
ex http://stackoverflow.com/questions/7375575/android-webview-v...
Re: IOS browsers have a 300ms click delay - But developers can bypass it
#8This is already well known, and the case with most browsers on touch devices. So terrible title, useful article.
Why is it a terrible title? I personally didn't know about the 300ms delay, and the title seemed to describe the article perfectly.
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.