Live data from Hacker News

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

developers.google.com

11–20 of 58 posts

Re: IOS browsers have a 300ms click delay - But developers can bypass it

#11
This is a known problem, but it's surprising how often it is overlooked. I personally use FastClick.js for this (http://assanka.net/content/tech/2011/08/26/fastclick-native-...), from the guys who did the Financial Times app.

You can see a demo here: http://assanka.net/content/tech/files/2011/08/fastclickdemo....

Of course, that only works if you are on an iOS device.

Re: IOS browsers have a 300ms click delay - But developers can bypass it

#13

This is a known problem, but it's surprising how often it is overlooked. I personally use FastClick.js for this ( http://assanka.net/content/tech/2011/08/26/fastclick-native-... ), from the guys who did the Financial Times app. You can see a demo here: http://assanka.net/content/tech/files/2011/08/fastclickdemo.... Of course, that only works if you are on an iOS device.

> Of course, that only works if you are on an iOS device.

It also works in Chrome Beta for Android.

Re: IOS browsers have a 300ms click delay - But developers can bypass it

#15

This is a known problem, but it's surprising how often it is overlooked. I personally use FastClick.js for this ( http://assanka.net/content/tech/2011/08/26/fastclick-native-... ), from the guys who did the Financial Times app. You can see a demo here: http://assanka.net/content/tech/files/2011/08/fastclickdemo.... Of course, that only works if you are on an iOS device.

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.

Re: IOS browsers have a 300ms click delay - But developers can bypass it

#16
post #15

This is a known problem, but it's surprising how often it is overlooked. I personally use FastClick.js for this ( http://assanka.net/content/tech/2011/08/26/fastclick-native-... ), from the guys who did the Financial Times app. You can see a demo here: http://assanka.net/content/tech/files/2011/08/fastclickdemo.... Of course, that only works if you are on an iOS device.

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 (b…

[deleted]

Re: IOS browsers have a 300ms click delay - But developers can bypass it

#18
post #13

This is a known problem, but it's surprising how often it is overlooked. I personally use FastClick.js for this ( http://assanka.net/content/tech/2011/08/26/fastclick-native-... ), from the guys who did the Financial Times app. You can see a demo here: http://assanka.net/content/tech/files/2011/08/fastclickdemo.... Of course, that only works if you are on an iOS device.

> Of course, that only works if you are on an iOS device. It also works in Chrome Beta for Android.

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).

Re: IOS browsers have a 300ms click delay - But developers can bypass it

#19
post #15

This is a known problem, but it's surprising how often it is overlooked. I personally use FastClick.js for this ( http://assanka.net/content/tech/2011/08/26/fastclick-native-... ), from the guys who did the Financial Times app. You can see a demo here: http://assanka.net/content/tech/files/2011/08/fastclickdemo.... Of course, that only works if you are on an iOS device.

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 (b…

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?

Post reply on HN