- From: adettenb via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Sep 2024 20:42:12 +0000
- To: public-pointer-events@w3.org
Hey @flackr, I reviewed the link you posted about `pointer-manipulation`, and it sounds like it would supplement `touch-action`? If I understand correctly, the benefit of the `pointer-manipulation` property would be that developers can specify which input device type(s) `[touch | mouse | stylus]` should allow the behavior(s) enabled by `touch-action: manipulation` (i.e., `[pan-[x|y] | pinch-zoom | +handwriting]`)? Unless `touch-action` would be deprecated and replaced by another property with a more appropriate name. I noticed you mentioned stylus writing in that comment, but I don't see a clear and concise way to separate the two behaviors (scrolling and handwriting) with `pointer-manipulation: [auto | none | touch | mouse | stylus]`, and `handwriting` doesn't see like it'd fit as a keyword for that property since it's not an input device type. For this proposal the goal would be to enable developers to specify whether scrolling and/or handwriting are allowed independently. So the developer could allow neither, either, or both (with UA defined precedence, likely handwriting over scrolling). cc: @mustaqahmed -- GitHub Notification of comment by adettenb Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/516#issuecomment-2341974181 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 September 2024 20:42:13 UTC