- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Feb 2021 16:14:10 +0000
- To: public-device-apis-log@w3.org
anssiko has just created a new issue for https://github.com/w3c/screen-wake-lock: == Auto-releasing wake lock depending on the user presence == Modern laptops in the market have hardware that allows the OS to dim or turn off the screen depending on the user presence. Full disclosure: Intel is working on [such technology](https://newsroom.intel.com/video-archive/video-ces-2021-intel-visual-sensing-technology-demo/). It appears [auto-releasing wake locks](https://w3c.github.io/screen-wake-lock/#dfn-auto-releasing-wake-locks) handles this case. However, I'd encourage the spec editors to check that this is appropriately hooked into the normative prose (unless "release a wake lock at any time" is fine). Also, maybe the [auto-releasing wake locks](https://w3c.github.io/screen-wake-lock/#dfn-auto-releasing-wake-locks) section could add an additional bullet for clarity: > A user agent may release a wake lock at any time, _for example when:_ [...] >* The operating system is configured to dim or turn off the screen based on the user presence state. It seems the concept of **applicable** is abstract enough with its "operating system permits" language: >The wake lock is [applicable](https://w3c.github.io/screen-wake-lock/#dfn-applicable-wake-lock) if the state of the operating system permits application of the lock (e.g. there is sufficient battery charge). @rakuco @kenchris for reactions. I can submit a PR after you've settled with the famous "in parallel" refactor. Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/300 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 5 February 2021 16:14:17 UTC