Summary: | Implement "touch-action:manipulation" Pointer Events CSS property to suppress 300ms touch > mouse compatibility events delay | ||
---|---|---|---|
Product: | WebKit | Reporter: | Patrick H. Lauke <redux> |
Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | benjamin, j.tangelder, rbyers, tonikitoo |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | https://dvcs.w3.org/hg/pointerevents/raw-file/tip/pointerEvents.html#the-touch-action-css-property |
Description
Patrick H. Lauke
2014-05-20 02:41:00 PDT
For further context, see also "Optimizations to remove 300ms touch > mouse events delay" https://bugs.webkit.org/show_bug.cgi?id=122212 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. 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. Sorry, that's bug 133112 that suggests adding all of touch-action. Let's merge :) *** This bug has been marked as a duplicate of bug 133112 *** Mass move bugs into the DOM component. |