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

Re: [wake-lock] Losing reference to a WakeLock object is a bug or intended behavior (#199)

From: Kenneth Rohde Christiansen via GitHub <sysbot+gh@w3.org>
Date: Wed, 01 May 2019 16:40:07 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-488336369-1556728806-sysbot+gh@w3.org>
* Remove the query() method. User agents should provide debugging tools to inspect the state of wake locks held by the page but it is unnecessary to expose these tools to script on the page itself.

https://github.com/w3c/wake-lock/commit/f569790bf86ffd2d30cc3017a8df0cca8dfe2df7

* Remove the abort() method in favor of the AbortSignal passed as part of WakeLockRequestOptions.

https://github.com/w3c/wake-lock/commit/5396f97487ea37df630648d8dccfa48f3dff20d7

* Throw an InvalidStateError if request() is called while the Promise returned by a previous call has not been resolved, or if the wake lock is not active.

https://github.com/w3c/wake-lock/commit/5396f97487ea37df630648d8dccfa48f3dff20d7

-- 
GitHub Notification of comment by kenchris
Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/199#issuecomment-488336369 using your GitHub account
Received on Wednesday, 1 May 2019 16:40:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 1 May 2019 16:40:09 UTC