- From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 Feb 2021 14:20:40 +0000
- To: public-device-apis-log@w3.org
@annevk I've pushed a few more commits. I think I've managed to solve everything, but I am not entirely sure doing things from a queued global task is enough to avoid race conditions and not being allowed to refer to global objects: * Switched to "queue a global task" * Switched to manipulating the `[[ActiveLocks]]` list only in the main event loop (from a queued global task in `WakeLock.request()` and without doing anything special in the "Release a wake lock" algorithm) * I think I've solved the page visibility issue by checking it inside the queued global task in `WakeLock.request()` (I'm adjusting the wording more broadly in #306). -- GitHub Notification of comment by rakuco Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/pull/299#issuecomment-779252992 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 15 February 2021 14:20:41 UTC