20311 2012-12-09 00:00:34 +0000 Clarify touch-action is only looked at during pointerdown 2013-01-12 14:58:30 +0000 1 1 1 Unclassified PointerEventsWG Pointer Events specification unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 jrossi jrossi art.barstow dfreedm public-pointer-events rbyers public-pointer-events-bugzilla oldest_to_newest 79769 0 jrossi 2012-12-09 00:00:34 +0000 You’re absolutely right. The intended design is that you only care about the value of touch-action on the target element of the pointerdown event. After that, it doesn’t matter what the value of touch-action is on elements you drag over. Additionally, I think it should be clarified that the value of touch-action is checked prior to dispatching pointerdown (e.g. modifications to touch-action during the event won’t be honored for that pointer). This, of course, is fundamental to ensure the performance optimizations for threaded scrolling that touch-action is intended to enable. -Jacob From: Daniel Freedman [mailto:dfreedm@google.com] Sent: Friday, December 7, 2012 2:34 PM To: public-pointer-events@w3.org Subject: Clarification of event generation with respect to touch-action In section 6.1, the description of "none" for touch-action states that touches that begin on those elements will not perform default actions. However, it is not stated if events may still be generated after the touch leaves that element with touch-action: none. In the MSPointerEvent implementation, further MSPointerMoves are dispatched to elements that can have touch-action: auto or touch-action: inherit. Is this what is expected for PointerEvents as well? Can this be made more explicit? Thanks! 80911 1 jrossi 2013-01-05 00:03:43 +0000 I believe there’s some language missing from the spec to clear things up. Here’s perhaps a more concise description of the behavior (emphasis on the last sentence): When a user touches an element, that element's -ms-touch-action property determines the default touch behaviors permitted for that contact, like panning or zooming. The touch behavior is then performed on the nearest ancestor element that is capable of that behavior, unless an intermediate ancestor element specifies that the behavior is not permitted. Would adding that clear things up? 80938 2 art.barstow 2013-01-05 12:57:28 +0000 A nit here: I think you want to remove the "ms" prefix for touch-action. 81028 3 rbyers 2013-01-08 04:51:56 +0000 That sounds reasonable to me, and is certainly an important detail that was missing. 81206 4 dfreedm 2013-01-10 21:52:16 +0000 That sounds good to me. Thanks! 81305 5 jrossi 2013-01-12 14:58:30 +0000 Great, I've made this change. https://dvcs.w3.org/hg/pointerevents/rev/dfe657176445 Resolution: http://www.w3.org/2013/01/08-pointerevents-minutes.html