FastClick

kalms wrote: post #4

yReply wrote: post #3

Why do the mobile devices not implement this by default?

A built in delay is making sure that you actually want to tap, and not swipe or double tap.

So it's safe to say this library might annoy users with accidental clicks.

Re: FastClick

#6

Post by kalms » Fri, Nov 23, 2012, 9:21 PM UTC

sergiotapia wrote: post #5

kalms wrote: post #4

Earlier quoted context omitted.

A built in delay is making sure that you actually want to tap, and not swipe or double tap.

So it's safe to say this library might annoy users with accidental clicks.

I guess that depends on how you use it. Probably unwise to use it on every link, but certain UI elements could benefit from it.

Re: FastClick

#7

Post by mrchess » Fri, Nov 23, 2012, 9:39 PM UTC

Nice implementation. For those not wanting to use a library you can achieve the same functionality by binding to the touchStart/touchMove events instead of 'click'.

Re: FastClick

#8

Post by isabre » Fri, Nov 23, 2012, 9:56 PM UTC

Great idea and nice implementation!

Re: FastClick

#9

Post by kordless » Fri, Nov 23, 2012, 10:04 PM UTC

sergiotapia wrote: post #5

kalms wrote: post #4

Earlier quoted context omitted.

A built in delay is making sure that you actually want to tap, and not swipe or double tap.

So it's safe to say this library might annoy users with accidental clicks.

Double clicks actually.

Re: FastClick

#10

Post by Geee » Fri, Nov 23, 2012, 10:34 PM UTC

Other methods mentioned in the thread such as Google's fast button or binding touchstart/touchend don't handle everything this does, such as input fields/checkboxes. This works also well with responsive AngularJS web apps without needing any custom directives for taps/clicks.