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

Re: [wake-lock] WakeLock and Page Life Cycle (#139)

From: Mrunal Kapade via GitHub <sysbot+gh@w3.org>
Date: Thu, 21 Mar 2019 01:54:22 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-475090267-1553133261-sysbot+gh@w3.org>
I am assuming Page Visibility is a sub topic of Page Lifecycle. One thing which spec should clarify is what would Wakelock's 'active' attribute reflect when page is not visible/backgrounded. Should there be another attribute like 'frozen'. For example in case of screen wake when tab is not visible _active_ would be _false_ but _frozen_ will be _true_ whereas in case of system wake lock _frozen_ would be _true_ but _active_ would also be _true_. This way that tab or app using wake lock will be aware of Wakelock's real status.

GitHub Notification of comment by mrunalk
Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/139#issuecomment-475090267 using your GitHub account
Received on Thursday, 21 March 2019 01:54:26 UTC

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