W3C home > Mailing lists > Public > public-device-apis-log@w3.org > December 2018

[wake-lock] What do the wakelocks actually do? (#138)

From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
Date: Wed, 12 Dec 2018 19:14:36 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-390369523-1544642075-sysbot+gh@w3.org>
jyasskin has just created a new issue for https://github.com/w3c/wake-lock:

== What do the wakelocks actually do? ==
Right now, the only specification I see for what happens while a wakelock is active is "The user agent acquires the wake lock by requesting the underlying operating system to apply the lock." This relies on each operating system to happen to define wakelocks that match the sketches in https://w3c.github.io/wake-lock/#wake-locks, and assumes that browsers won't introduce similar power-saving abstractions between the webpage and the OS.

Ideally, the kinds of sleeps that wakelocks prevent would be explicitly described in HTML and other specs, and wakelocks would remove the permission to sleep like that. There may be quicker ways to still specify this in a way that's independent of the OS.

Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/138 using your GitHub account
Received on Wednesday, 12 December 2018 19:14:37 UTC

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