- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Sep 2021 00:41:47 +0000
- To: public-device-apis-log@w3.org
The continued innovation in this space makes me reconsider the use case for expressing a high-level concept like "posture" instead of low-level details about the screen geometry and positioning as proposed by the [Window Segments Enumeration API](https://github.com/webscreens/window-segments/blob/master/EXPLAINER.md) and hints about which input modes (touch, mouse, keyboard, pen, etc.) are available or preferred given the device configuration. The question I'd like to see answered is whether these high-level postures provide additional information or whether web content would be more adaptable to new device configurations if it made decisions based on the individual low-level properties. -- GitHub Notification of comment by reillyeon Please view or discuss this issue at https://github.com/w3c/device-posture/issues/94#issuecomment-926262488 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 September 2021 00:41:48 UTC