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

Re: [wake-lock] A broken script shouldn't be able to put the whole system in a broken state until page reloaded, I think something is broken. (#151)

From: Reilly Grant via GitHub <sysbot+gh@w3.org>
Date: Fri, 01 Mar 2019 21:31:28 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-468818679-1551475887-sysbot+gh@w3.org>
I think the question is how we define "a broken script." If the page becomes unresponsive then I would consider dropping all of its wakelocks but otherwise it seems completely reasonable for a page to take a wakelock and not release it for its entire lifetime. Take as an example an application like Google Slides. When you enter presentation mode it is completely reasonable to have a screen wakelock that is held for as long as the presentation is being displayed, no matter how long the user pauses between slides.

Even a system wakelock may make sense to leave active even if the page is not in focus. Take for example an application performing some computation. If I switch to a different tab while I wait and then get up to get a coffee should the script be paused by the system going to sleep?

-- 
GitHub Notification of comment by reillyeon
Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/151#issuecomment-468818679 using your GitHub account
Received on Friday, 1 March 2019 21:31:30 UTC

This archive was generated by hypermail 2.3.1 : Friday, 1 March 2019 21:31:30 UTC