Re: [pointerevents] [touch actions] handwriting manipulation type to distinguish panning (#516)

+1 for `touch-action: handwriting pan` or similar, combined with UA defined precedence would allow both handwriting and scrolling (for stylus and touch), and devices that don't support handwriting will simply have scrolling. If there were a more granular mechanism like we discussed on call we could also filter specific actions by device type, and provide a fallback mechanism for example.

An unfortunate side-effect is any sites that might want handwriting which already specify `touch-action` would need to take action to enable this feature, however this is by design for `touch-action` as far as I can tell.

On the [BlinkOn slide #23](https://docs.google.com/presentation/d/1OkIqs5iOYfiLAycCvyUFBucQE4QoIPCViDV9GKZjdGo/edit?usp=sharing), I included this concept with a format similar to `manipulation: DEVICE_TYPE(ACTION_LIST) ...;`.
This was the same idea as the earlier proposed `pointer-action`, but I include other non-pointer "device types" like "eye" for eye-tracking, "positional-tracking" for VR/AR controllers, and "voice" for microphone input. Some of these input device types were mentioned in another similar proposal.

I'm imagining this CSS `manipulation` or `pointer-action` property optionally allowing device filtering and multiple actions per filter. Possibly even allowing the defined order to declare which takes precedence rather than leaving it UA defined. I think UA defined precedence probably makes the most sense though, it'd be much easier to implement at least.
e.g.,
* If an author only wanted "stylus device" handwriting and "touch device" pan/zoom:
  * `manipulation: stylus(handwriting) touch(pan zoom) none`
* If an author only wanted "stylus device" handwriting and "any device" pan/zoom:
  * `manipulation: stylus(handwriting) pan zoom`
  * `manipulation: stylus(handwriting) any(pan zoom)`

For the PR I'll be drafting this week, I plan to simply add `handwriting` as a keyword with UA defined precedence
I think the other options are worth pursuing in the future, but will likely be a replace and deprecate `touch-action`.

-- 
GitHub Notification of comment by adettenb
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/516#issuecomment-2412604482 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 15 October 2024 00:54:51 UTC