Documentation clarifying hammer.js vs. 300ms delay

[eliotsykes]

Docs would be improved with some clarification in the wiki on if hammer.js takes away the 300ms click delay or if another solution (e.g. fastclick) is recommended (or perhaps it isn't?) or how hammer.js can be configured to remove the delay.

If you can clarify it here or point me in the right direction, I'm happy to write the wiki page.

Kind regards and thanks for making hammer.js!
Eliot

[shai126]

+1

[jtangelder]

Hammer doesnt remove the click delay for the click events, but, it does 'remove' it when you'll just use tap for the clicking on links.

[eliotsykes]

Ok, so would hammer.js benefit from a wiki page to document this? If yes, how does the outline below sound?

Title: Removing click delays

Sections:

1. What the click delay is and why it exists
2. Remove click delay with hammer.js' tap event (overview and examples of using it on anchors and buttons)
3. (Not?) using hammer.js and fastclick.js together (is this a bad idea?) (example)

[laktak]

+1

[porjo]

+1

[ganchenkor]

+1

[jtangelder]

I will look into this! 👍

[StreetStrider]

So, for clarification:

1. using tap is well enough to eliminate delay.
2. fastclick and hammer do not intervene interfere with each other.
   As many people above, I think documentation should mention this, too. Thanks.

[xmnboy]

The term "intervene" is confusing here. Do you mean that fastclick and hammer do not interfere with each other, so they can be used together? Or, do you mean that fastclick and hammer will interfere with each other, so they should not be used together?

The reason I ask is because the term "intervene" is an active verb, it means to actively interfere or intercede. The prior comments also are not clear regarding whether or not it is okay to use the two (hammer and fastclick) libraries together.

[StreetStrider]

@xmnboy, hi.
I mean the first one. Sorry for confusing. So both of them would not break each other, and they can be used together.

[xmnboy]

Thanks for the clarification. 👍

[corgrath]

Did a page get created for this?

[runspired]

There is no page for this. Using tap as a fastclick presents other issues. You'll usually need to bust the clicks that do occur later, but clicks on inputs and buttons on mobile often need to be allowed. There's lots of tricky corner cases, so in general with the current (2.0.4) version of Hammer, tap is not a drop in replacement for fastclick.

Closing this in favor of actually producing a solution to these cases in #808