150469 2015-10-22 13:40:55 -0700 remove 350ms touch > mouse events delay for width=device-width viewport 2015-10-27 17:01:28 -0700 1 1 1 Unclassified WebKit UI Events WebKit Nightly Build iPhone / iPad Unspecified RESOLVED DUPLICATE 150604 P2 Normal --- 1 redux webkit-unassigned hello irae m.goleb+bugzilla nekr.fabula rbyers webkit wenson_hsieh oldest_to_newest 1135808 0 redux 2015-10-22 13:40:55 -0700 (opening this as a separate issue from https://bugs.webkit.org/show_bug.cgi?id=122212) Chrome [1], Firefox and MS Edge currently remove the 300-350ms delay between touchend and the mouse compatibility events (see [2]) for "mobile optimized" pages that have a viewport of width=device-width. Pages are still zoomable using pinch-to-zoom, but not double-tap-to-zoom. Supporting this in iOS would obviate the need for mobile sites to use tricks such as fastclick.js Although a more declarative method will now be available with touch-action:manipulation [3], it may still be worth considering this for compatibility with the other major browsers (and the fact that it's arguably the path of least resistance for developers: support for this would mean that sites which currently use width=device-width and fastclick.js can simply remove the latter, vs removing fastclick AND explicitly adding touch-action:manipulation). [1] https://developers.google.com/web/updates/2013/12/300ms-tap-delay-gone-away?hl=en [2] http://patrickhlauke.github.io/touch/tests/results/#suppressing-300ms-delay [3] https://bugs.webkit.org/show_bug.cgi?id=149854 1135812 1 redux 2015-10-22 13:48:17 -0700 Copying over a useful comment from rbyers from https://bugs.webkit.org/show_bug.cgi?id=122212 which provides some hard data "Some usage data from Chrome which may be helpful in having a data-oriented debate here: - only 0.6% of taps lead to a double tap - rises to 3.5% considering only sites where double tap is enabled - 75% (and increasing) of pages loaded on Android have a mobile viewport - 84% of taps (and increasing) occur on pages with a mobile viewport" 1136988 2 wenson_hsieh 2015-10-27 17:01:28 -0700 *** This bug has been marked as a duplicate of bug 150604 ***