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

[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: Kenneth Rohde Christiansen via GitHub <sysbot+gh@w3.org>
Date: Fri, 01 Mar 2019 16:35:34 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-416183501-1551458132-sysbot+gh@w3.org>
kenchris has just created a new issue for https://github.com/w3c/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. ==
This is from Mounir.

Maybe @slightlyoff has additional ideas and comments.

I haven't thought much about this yet, but it seems to always kind of be the case. We cannot trust pages to ever do the right thing - or ever release the lock on their own.

Mitigation strategies
- Force having a AbortSignal (not make it optional) - still won't force the page to do the right thing with it
- Page visibility change / focus should already (didn't check that spec text yet) release the lock
- We can make unresponsive pages (maybe via page life cycle) auto-release the lock

Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/151 using your GitHub account
Received on Friday, 1 March 2019 16:35:35 UTC

This archive was generated by hypermail 2.3.1 : Friday, 1 March 2019 16:35:35 UTC