- From: Jacob Rossi <Jacob.Rossi@microsoft.com>
- Date: Sat, 19 Jan 2013 00:57:19 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>
- CC: "L. David Baron" <dbaron@dbaron.org>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>, "www-style@w3.org" <www-style@w3.org>
>On Fri, Jan 18, 2013 at 4:23 PM, Jacob Rossi <Jacob.Rossi@microsoft.com> wrote: >> I think this misses the nuance of the nearest ancestor having both a touch behavior and touch-action: none, in which case you do not execute the action. How about: >> >> When a user touches an element, the effect of that touch is determined by the 'touch-action' property and the default touch behaviors on the element and its ancestors. To determine the effect of a touch, find the nearest ancestor (starting from the element itself) that either has a default touch behavior or that has "touch-action: none". If that element has “touch-action: none”, do nothing. Otherwise, allow the element to start considering the touch for the purposes of executing its default touch behavior. >> >> When a UA determines a touch should trigger a behavior on this element (by methods outside the scope of this spec), then it must cancel that pointer by dispatching pointercancel and pointerout events.> > >Sounds good! Awesome. Opened a bug on this: Bug 20710 - Clarify touch-action processing model https://www.w3.org/Bugs/Public/show_bug.cgi?id=20710 We'll likely discuss at our next telecon on Tuesday to make sure we're all in agreement. -Jacob
Received on Saturday, 19 January 2013 00:58:56 UTC