This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20710 - Clarify touch-action processing model
Summary: Clarify touch-action processing model
Status: RESOLVED FIXED
Alias: None
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Jacob Rossi [MSFT]
QA Contact: Pointer Events Bugzilla list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-19 00:54 UTC by Jacob Rossi [MSFT]
Modified: 2013-01-29 03:24 UTC (History)
1 user (show)

See Also:

Attachments

Description Jacob Rossi [MSFT] 2013-01-19 00:54:54 UTC 
Per CSS WG feedback, the following text should be added to clarify the processing model for touch-action:

> 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.

http://lists.w3.org/Archives/Public/public-pointer-events/2013JanMar/0026.html
Comment 1 Jacob Rossi [MSFT] 2013-01-29 03:24:28 UTC 
Change made as requested.

https://dvcs.w3.org/hg/pointerevents/rev/1c4dbd02863a

RESOLUTION: http://www.w3.org/2013/01/22-pointerevents-minutes.html#item02