W3C home > Mailing lists > Public > public-device-apis-log@w3.org > October 2019

[wake-lock] Hide failure to acquire a screen wake lock (#247)

From: Reilly Grant via GitHub <sysbot+gh@w3.org>
Date: Wed, 23 Oct 2019 22:48:31 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-511611116-1571870910-sysbot+gh@w3.org>
reillyeon has just created a new issue for https://github.com/w3c/wake-lock:

== Hide failure to acquire a screen wake lock ==
The [security and privacy considerations](https://w3c.github.io/wake-lock/#security-and-privacy-considerations) section highlights that failure to acquire a wake lock can be used as a signal to indicate that the system is in low power mode. At least in the case of screen wake locks this explicit information leakage is unnecessary. The experimental Blink implementation does not currently implement this behavior. Aside from when permission has been explicitly denied by the user wake lock acquisition always appears to succeed even if the underlying operating system denies the lock.

If a screen wake lock is not acquired then the screen could go to sleep. This is observable by the page as a `pagevisibility` event. This may be distinguishable from the user manually locking their screen because it occurs after a precise interval since the last user input.

Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/247 using your GitHub account
Received on Wednesday, 23 October 2019 22:48:33 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:57 UTC