-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto-releasing wake lock depending on the user presence #300
Comments
I'm not sure we need this (given how broad "release a wake lock at any time" is), but I wouldn't object to seeing a proposal for changes or maybe added as an example? |
anssiko
added a commit
that referenced
this issue
Mar 23, 2021
rakuco
pushed a commit
that referenced
this issue
Apr 5, 2021
* Update auto-releasing wake lock examples Fix #300 Co-authored-by: Marcos Cáceres <[email protected]>
(Connecting the dots: some user presence use cases were discussed in the DAS WG - 2021 Q2 virtual meeting. The Screen Wake Lock API editorial update #310 that landed was to clarify interaction with such a user presence implementation.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It appears 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 section could add an additional bullet for clarity:
It seems the concept of applicable is abstract enough with its "operating system permits" language:
@rakuco @kenchris for reactions. I can submit a PR after you've settled with the famous "in parallel" refactor.
The text was updated successfully, but these errors were encountered: