- From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Jun 2024 09:30:04 +0000
- To: public-device-apis-log@w3.org
> So you are thinking a bit like WakeLock where it is the developers responsibility to start observation again. I guess that could work. Ideally, we could take of all this behind the scenes and just start providing data again once the document becomes fully active, I just don't know how to do it properly from a spec perspective: - No other spec seems to add steps to "reactivate a document" at the moment - If attempting to get pressure data again fails, there is no way to notify users - From a spec perspective, there isn't a way to differentiate between "this document is going into the bfcache and may be reactivated in the future" and "this document is going away forever", which I thought would be necessary to decide whether to fully release resources or not. Pragmatically, merging #276 helps move #265 forward, but it'd be nice to revisit this issue later. -- GitHub Notification of comment by rakuco Please view or discuss this issue at https://github.com/w3c/compute-pressure/issues/275#issuecomment-2147053142 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 4 June 2024 09:30:05 UTC