- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Sat, 22 May 2021 16:06:27 +0000
- To: public-pointer-events@w3.org
The following commits were just pushed by patrickhlauke to https://github.com/w3c/pointerevents: * Clarify the rationale and purpose of touch-action (#376) * Clarify the rationale and purpose of touch-action - moved the note about viewport manipulation from the "Declaring candidate regions for default direct manipulation behaviors" section directly to the "Attributes and Default Actions" section, and made the text normative rather than informative (by not having it as a note, but actual part of the normative prose) - expanded the sentence to more clearly convey what this means - by not having viewport manipulations treated/counted as a default action for pointer events, panning/zooming can't be prevented by cancelling a pointer event, and that instead authors must use `touch-action` - tweaked the intro section to "Declaring candidate regions for default direct manipulation behaviors" to reiterate this concept/rationale - removed one confusing instance of "default behavior" and changed to just "behavior" in a note in the touch-action section Closes https://github.com/w3c/pointerevents/issues/366 https://github.com/w3c/pointerevents/issues/368 * Already add this PR to revision history ... saves time for when it gets (hopefully) merged. Needs to be listed as it is substantive (turns the informative note into a normative requirement) * Removing two more instances of "default ... behaviour" there are still a few cases of "default direct manipulation behaviour" present in prose, but I think in those contexts, they make sense to be used and don't confuse matters with "default action" by Patrick H. Lauke https://github.com/w3c/pointerevents/commit/42e4be69d6428d55e9f002aa5bdfb3e71cbb1261 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 22 May 2021 16:06:31 UTC