Is this library maintained?

[paulfalgout]

@mattcg is listed as the maintainer at FT labs, but no longer works there.

And despite quite a few open PRs, the last commit on Master was in Jan.

Is the project abandoned?

[dsonet]

Same doubt.

[armoucar]

+1.

Calling in other big contributor: @matthew-andrews

[nonameolsson]

+1

[atom-project]

+1

[matthew-andrews]

We use it in production across all our sites… and will fix serious bugs with it that affect us. It's hard to test all of the incoming contributions because it's nobody's focus at the FT anymore. Thankfully browsers are starting to catch up and native browser solutions to the problems FastClick solves are now available in Chrome, Firefox, Blackberry… Hopefully Safari will follow soon.

But you're right to ask this. We've let you down and we need to try harder :disappointed:.

[nonameolsson]

@matthew-andrews Thank you for your fast answer :blush: I haven't used this on so many pages. So the latest versions of Chrome, Firefox and Blackberry has fixed this. Is the only purpose now to use it for fixing Safari?

[matthew-andrews]

@nonameolsson I believe so yes, and old browsers of course.

[davidgoli]

I would nominate https://github.com/ftlabs/fastclick/issues/358 as THE single most pressing bug you have right now. There are a number of proposed pull requests to get around this. I would nominate https://github.com/ftlabs/fastclick/pull/342 or https://github.com/ftlabs/fastclick/pull/361 as the best fix candidates.

[paulfalgout]

By far the biggest pressing bug in my opinion is https://github.com/ftlabs/fastclick/pull/384

The others don't seem to directly affect users, but this one has a super strange user experience for current iOS devices

[xdragus]

I was starting to question this too especially when IOS8 errors start populating the issues thread.

Since then I've had to disable for IOS 8.xx and leave it in for older browser support.

But thank you FT for all you've done for us.

[roryhardy]

If this project isn't going to be actively maintained anymore by FT would it be possible to pass it on to a new owner(s) or add core contributors to continue development or at least post a notice in the project README to give a heads up to those looking to use it?

[fwebdev]

There is a fresh Fix in Webkit Nightly. But iOS Version ist still "Unspecified". https://bugs.webkit.org/show_bug.cgi?id=149968

So maybe there is no need for Fastclick in the Future anymore :-)

[jmarchello]

Thankfully browsers are starting to catch up and native browser solutions to the problems FastClick solves are now available in Chrome, Firefox, Blackberry…

What are these solutions and how can I utilize them? I'm running the latest version of Chrome on iOS 9 and still suffer the 300 ms delay after tap. Thanks?

[moodysalem]

If you're using React, I wrote a very small component (<200 lines) that is working well for me. It doesn't have the issues in #358 or #384

https://github.com/moodysalem/react-fastclick

[wulfsolter]

@moodysalem Link broken?

[moodysalem]

@wulfsolter I fixed the link, https://github.com/moodysalem/react-fastclick

Deployed to npm as react-fastclick-alt

[aidonsnous]

I am developping an app using phonegap using bootstrap framework. So Do you mean that there is no longer the 300ms delay in browser ? What is the use of React?

[paulfalgout]

The last browser I am aware of to have the 300ms delay was Safari.. but as of 9.3 that is removed. So you really only need fastclick for legacy browsers, however this will probably be an issue for a little while until people upgrade.

[davidgoli]

Due to lack of updates, I recommend avoiding this library in favor of Hammer Time: https://github.com/hammerjs/hammer-time