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

Re:IOS browsers have a 300ms click delay - But developers ca... by mattcg on Friday June 08, 2012 @06:27AM (#4083571)

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.

[ Parent | on HN ]

Re:IOS browsers have a 300ms click delay - But developers ca... by fiznool on Friday June 08, 2012 @07:16AM (#4083666)

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?

[ Parent | on HN ]

Re:IOS browsers have a 300ms click delay - But developers ca... by Danieru on Friday June 08, 2012 @09:40AM (#4084094)

They only support Windows with IE10 as he said above?

[ Parent | on HN ]

Re:IOS browsers have a 300ms click delay - But developers ca... by fiznool on Saturday June 09, 2012 @07:09AM (#4087828)

Yep, saw that, just wondering if there are any insights into why it won't work for WP7.5, in case it is a work in progress or a complete no-hope.

[ Parent | on HN ]