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

Re: [wake-lock] Add another condition to WakeLock.request()'s "abort when" block. (#227)

From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
Date: Wed, 21 Aug 2019 11:27:18 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-523415500-1566386836-sysbot+gh@w3.org>
@reillyeon it's been a while since I filed #222 and landed https://chromium-review.googlesource.com/c/chromium/src/+/1651821 in Blink; I've written here that only changes in page visibility have an effect even though a loss of full document activity also operates on `[[ActiveLocks]]`. Can you double-check if this makes sense as-is?

GitHub Notification of comment by rakuco
Please view or discuss this issue at https://github.com/w3c/wake-lock/pull/227#issuecomment-523415500 using your GitHub account
Received on Wednesday, 21 August 2019 11:27:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:34:28 UTC