W3C home > Mailing lists > Public > public-device-apis-log@w3.org > June 2017

[wake-lock] Clarify state of screen lock after manual lock & unlock

From: Jake Archibald via GitHub <sysbot+gh@w3.org>
Date: Wed, 07 Jun 2017 09:50:30 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-234153636-1496829029-sysbot+gh@w3.org>
jakearchibald has just created a new issue for https://github.com/w3c/wake-lock:

== Clarify state of screen lock after manual lock & unlock ==
Use case: 

1. I'm using route navigation, which as requested a screen lock, which I have granted.
1. I'm somewhat familiar with the route, so I turn the screen off to preserve power (audio is enough)
1. Oh no! The road is closed, I need to divert!
1. I turn the screen back on.

**Will I need to unlock my phone (pin/pattern etc)** or will the "on" button take me straight back into the app? On my Android phone, Endomondo seems to require unlocking, whereas Google Maps Navigation does not. I can't see anything in the spec about this.

**Will the screen lock be automatically reinstated** or will the screen automatically turn off as if the screen lock was never granted? It seems like the intent is to reinstate, but this bit of wording makes it seem ambiguous:

> The screen wake lock must not be applicable when the device is manually locked by the user.

Maybe change that "when" to a "while"?

Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/102 using your GitHub account
Received on Wednesday, 7 June 2017 09:50:36 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:18:53 UTC