133114 2014-05-20 02:41:00 -0700 Implement "touch-action:manipulation" Pointer Events CSS property to suppress 300ms touch > mouse compatibility events delay 2019-02-06 09:19:17 -0800 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 133112 https://dvcs.w3.org/hg/pointerevents/raw-file/tip/pointerEvents.html#the-touch-action-css-property P2 Normal --- 1 redux webkit-unassigned benjamin j.tangelder rbyers tonikitoo oldest_to_newest 1010439 0 redux 2014-05-20 02:41:00 -0700 Although there seems to be no immediate desire to implement the full Pointer Events specification (see https://bugs.webkit.org/show_bug.cgi?id=105463), it may be worth considering at least supporting the touch-action:manipulation CSS property/value. This recent addition (the "manipulation" value) to the Pointer Events specification is used - in essence - to allow developers to suppress the classic 300ms delay present on touchscreen devices that by default allows for "double-tap to zoom", while retaining other abilities such as scrolling and pinch-to-zoom. It offers a compromise to the often drastic preventDefault() commonly used in touch-optimised applications (which does remove the 300ms delay, but also kills any other default interactions). touch-action:manipulation is on track to be rolled out in both Firefox and Chrome - see "Bug 979345 - Implement "touch-action: manipulation" CSS value for Pointer Events" https://bugzilla.mozilla.org/show_bug.cgi?id=979345 "Issue 349016: Add support for touch-action: manipulation" https://code.google.com/p/chromium/issues/detail?id=349016 1010440 1 redux 2014-05-20 02:44:33 -0700 For further context, see also "Optimizations to remove 300ms touch > mouse events delay" https://bugs.webkit.org/show_bug.cgi?id=122212 1010445 2 j.tangelder 2014-05-20 02:59:39 -0700 I'm more interested in the fact that this makes it easier to detect gestures, without doing al kinds of crazy tricks in the event handlers. That it has the ability to remove the 300ms is cool, but not the main function of the property. 1010483 3 rbyers 2014-05-20 07:16:15 -0700 See also bug 133114 which proposes adding all of touch-action to WebKit. Note that there's an argument to be made that disabling double-tap zoom on portions of a UI (or even on some pages but not others) is inconsistent and leads only the user confusion. The counter-argument is that web developers are largely doing this already using libraries like FastClick (I believe FastClick or something like it is in use on most major mobile-optimized websites). But those libraries come with other downsides (bugs, perf impact, loss of touch adjustment, other browser UI features unnecessarily disabled, etc.). So my opinion is that we might as well give developers a simple reliable switch to clearly toggle the behavior they otherwise struggle to change. 1010484 4 rbyers 2014-05-20 07:17:24 -0700 Sorry, that's bug 133112 that suggests adding all of touch-action. 1010531 5 benjamin 2014-05-20 09:59:24 -0700 Let's merge :) *** This bug has been marked as a duplicate of bug 133112 *** 1503352 6 lforschler 2019-02-06 09:19:17 -0800 Mass move bugs into the DOM component.