README.md

The issue:

..mobile browsers will wait approximately 300ms from the time that you tap the button to fire the click event. The reason for this is that the browser is waiting to see if you are actually performing a double tap.

(from a new defunct https://developers.google.com/mobile/articles/fast_buttons article)

touch-action CSS property can be used to disable this behaviour.

touch-action: manipulation The user agent may consider touches that begin on the element only for the purposes of scrolling and continuous zooming. Any additional behaviors supported by auto are out of scope for this specification.

– https://developer.mozilla.org/en-US/docs/Web/CSS/touch-action#Values

touch-action is now supported by all major mobile browsers.

Note that iOS 9.3 has not been released yet. (2016 02 13)

In ./webpack.js I am first detecting if the touch-action property is supported. If it is, I am using it to set the style of document.body. If it is not, then I am using webpack require.ensure to download FastClick polyfill to fix the issue.

webpack.js

if ('touchAction' in document.body.style) {
    document.body.style.touchAction = 'manipulation';
} else {
    require.ensure(['fastclick'], (require) => {
        const FastClick = require('fastclick');

        window.addEventListener('load', () => {
            FastClick.attach(document.body);
        });
    }, 'fastclick');
}

Awesome. Thanks a lot for sharing this GIST.

@neilbayor Not just Chrome. It disables the delay in a range of browsers http://patrickhlauke.github.io/touch/tests/results/#suppressing-300ms-delay. If the page is responsive (mobile-friendly), the viewport meta tag is enough, according to that table. Not sure what the fascination with touch-action is, but the table shows that it’s not needed. (Please don’t cargo cult.)

Hey @gajus. Thank you for sharing!
I've just published a module that does the same as your gist, but loads FastClick from CDN when needed https://github.com/alekseykulikov/touch-action

Double tap was removed from major browsers for sties using width=device-width.

• Chrome was first: https://developers.google.com/web/updates/2013/12/300ms-tap-delay-gone-away
• Firefox did this 2 years ago: https://bugzilla.mozilla.org/show_bug.cgi?id=941995
• Safari followed about 2 months ago: https://bugs.webkit.org/show_bug.cgi?id=150604

So touch-action is probably only important for Windows Phone (if you care for a dying platform). As seems touch-action support is actually worse in terms of mobile share.

@simevidas not entirely, ng-click still has the delay for me even with the viewport tag

@Itrulia Sounds like an issue with Angular. I can debug if you make a demo.

@simevidas Yeah just found why it happened on that one site (I asked myself too why it happened), because it had 1-2px of horizontal scrolling :/

Awesome, thanks for this! BTW you got mentioned in a smashing magazine post.

@simevidas

If the page is responsive (mobile-friendly), the viewport meta tag is enough, according to that table. Not sure what the fascination with touch-action is, but the table shows that it’s not needed.

Personally, I like the explicit, declarative nature of having a rule in my styles that clearly states the browser's intended behavior, rather than relying on magical heuristics (even if they're becoming universal) like width=device-width. But you're correct that pragmatically, all main browsers are (finally, once iOS 9.3 is out) adopting this optimisation. Still, I'm hoping Firefox/Android (the last major player to drag its heels) will implement this soon.

As a side note, on desktop/laptop devices with touchscreen, Microsoft Edge also has double-tap to zoom, and any viewport setting has no effect...so in this scenario, touch-action is the only reliable method of suppressing the click delay. Other browsers (Chrome, Firefox, ...) don't seem to (yet) have double-tap to zoom on these platforms...but if they decide to implement it, they'll likely also ignore viewport the same way. So one saving grace of using both mobile viewport and touch-action is the potential future-proofing for this case.

I know this is old, but as I came across this page looking for advice I thought I would update.

touch-action: manipulation is still necessary to remove the tap delay in Chrome (and presumably others) on touch screens on Windows 10 laptops such as the Dell XPS 13. https://patrickhlauke.github.io/touch/tests/results/#suppressing-300ms-delay