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

[wake-lock] Page visibility and browsing contexts (#206)

From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
Date: Thu, 09 May 2019 14:27:07 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-442266120-1557412025-sysbot+gh@w3.org>
rakuco has just created a new issue for https://github.com/w3c/wake-lock:

== Page visibility and browsing contexts ==
In the description of the `request()` method, the spec says: _If lock's type is "screen" and the Document of the top-level browsing context is hidden, reject promise with a "NotAllowedError" DOMException, and run abort the request steps_, and in the section about page visibility handling it says: _When the user agent determines that the visibility state of the Document of the top-level browsing context changes, it must run these steps_.

What does this mean for documents which are not the top-level browsing context, like an iframe? Should `request()` fail if it's not visible but the top-level frame is? What happens when an iframe holding a lock becomes hidden but the top-level frame doesn't?

Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/206 using your GitHub account
Received on Thursday, 9 May 2019 14:27:09 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 9 May 2019 14:27:10 UTC