- From: Alexis Menard via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jan 2022 16:08:33 +0000
- To: public-device-apis-log@w3.org
@voxpelli I'm familiar with what you said and the basic premise of a stylus. All your bullet points are covered with the PointerEvents. Now my comment was about "if stylus is the primary input" and UX changes. Let's step back. How an OS/Device can determine if the stylus is the primary input provided that the moment it goes out of range (few centimeters) the OS can't see it, but it can come back anytime (meaning the user is just lifting its palm). The hover feature works only with very close proximity of the screen. Therefore, changing the UX doesn't make sense because it will keep wobbling between stylus-primary to touch-primary. Microsoft can comment but even if the stylus entertains some bluetooth connection it's only to enable gestures like double click to launch an app (even if you're not in close proximity of the touch digitizer). All the event delivery is done through the digitizer therefore suffering the same limitation as I describe above. -- GitHub Notification of comment by darktears Please view or discuss this issue at https://github.com/w3c/device-posture/issues/96#issuecomment-1016621487 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 January 2022 16:08:35 UTC