W3C home > Mailing lists > Public > public-device-apis-log@w3.org > January 2020

[wake-lock] Navigation and maintaining locks (#249)

From: Martin Thomson via GitHub <sysbot+gh@w3.org>
Date: Wed, 22 Jan 2020 01:29:37 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-553254061-1579656575-sysbot+gh@w3.org>
martinthomson has just created a new issue for https://github.com/w3c/wake-lock:

== Navigation and maintaining locks ==
Lets say that a page wants to navigate and maintain a lock.  Is that something the spec should cover?

It seems necessary for a lock to be released when a page navigates, which means that if the lock permission grant is coupled to an engagements gesture the page loses.  Does this API create unnecessary incentives to build single-page apps?

Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/249 using your GitHub account
Received on Wednesday, 22 January 2020 01:29:38 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 01:29:39 UTC