- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Aug 2021 01:42:38 +0000
- To: public-device-apis-log@w3.org
Would this be the same as the document becoming non-fully active? I think the "[handling document loss of full activity](https://w3c.github.io/screen-wake-lock/#handling-document-loss-of-full-activity)" might be wrong at the moment... paraphrasing the spec: 1. if the document is no longer fully active, [release the wake lock](https://w3c.github.io/screen-wake-lock/#ref-for-dfn-release-a-wake-lock-5). 2. Ask the OS to release the lock. 3. 🧨 Fire an event named "release". Shouldn't step 3 wait for the document to become fully active again before firing the event? (also, fire the event should probably be queued... we might want to separate "release the lock" from the actual "release" event being fired). CC @rakuco. -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/139#issuecomment-900747568 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 August 2021 01:42:41 UTC