- From: Antoine Quint via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Sep 2019 16:29:26 +0000
- To: public-pointer-events@w3.org
> "Once a touch action has been started, and the user agent has already determined whether or not the action should be handled as a user agent touch behavior, any changes to the relevant touch-action value will be ignored for the duration of the touch action" My interpretation of this paragraph does not relate to the issue here. To me, what this means is that a change to the `touch-action` value has no bearing during a given touch gesture. I think we have two options: 1. Specify in Pointer Events that if a single panning direction is specified with the `touch-action` property that initially panning in a contrary direction should prevent scrolling in the direction specified by `touch-action`. This is the current Chrome behavior and I expect we will implement this in WebKit shortly. 1. Specify another CSS property or extend the definition of an existing CSS property to specify whether a fragment may have directional locking for scrolling. At any rate I believe we *must* specify something since the spec as-is is at best unclear but in my opinion does not sufficiently define user-agent behavior for such interactions causing interoperability issues for what I believe to be a reasonable design as demonstrated in the test. -- GitHub Notification of comment by graouts Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/303#issuecomment-530459317 using your GitHub account
Received on Wednesday, 11 September 2019 16:29:27 UTC