W3C home > Mailing lists > Public > public-pointer-events@w3.org > January to March 2013

RE: Request for Comments: Pointer Events spec's touch-action CSS property

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>
Message-ID: <a687475bbe904b629e6c7c950d634d6b@BN1PR03MB021.namprd03.prod.outlook.com>
>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

We'll likely discuss at our next telecon on Tuesday to make sure we're all in agreement.

Received on Saturday, 19 January 2013 00:58:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:24 UTC