- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jan 2025 16:28:28 +0000
- To: public-pointer-events@w3.org
We discussed this in the call. There was a general concern about the behavior for legacy content (for which handwriting was not something developers knew they should opt into). * For pre-existing `pointer-events: none` content, developers expect to be disabling and manually handling pointer events. This will work as expected with this proposal as `none` will disable handwriting. * For pre-existing `pointer-events: pan-x` (or pan-y) content, developers expect to be disabling and handling scrolling in the other direction. However, it's less clear whether or not they would have wanted to disable handwriting. There were concerns about cases where you might want a different action for touch and stylus, note that no UA currently will start handwriting on touch so by default touch will scroll where a stylus will start writing. However, you would not be able to specify that touch should pan but a stylus does nothing. For this, we expect that #203 would allow differentiating. Further, we expect that developers would like to be able to opt into a different default action for devices capable of multiple, #512 suggests some extension for this in the future. We think that we might be able to defer to these other issues and suggest that authors use new properties there to both fix some of the oddities of the touch-action property and allow for the full expressivity of desired behaviors and for now focus on defining something for touch-action that best handles legacy content. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/516#issuecomment-2624973859 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 January 2025 16:28:29 UTC