- From: Mitchell Wills via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Jun 2020 17:28:11 +0000
- To: public-device-apis-log@w3.org
Are there any plans to continue the work for system wakelocks? I would definitely like to see this happen to support applications that are doing significant amounts of computing or interacting with hardware (via WebUSB/WebSerial). Especially when interacting with hardware it can be important to try to not interrupt communications when possible (even if the tab is in the background). Additionally, if would be nice if acquiring a lock prevented the browser from performing additional throttling/freezing on the tab, but not sure if that is more of an implementation detail (may not be the right api for it either). To add more context my specific use case is acquiring a system wake lock during the Android device flashing process on https://flash.android.com. The flashing process should ideally not be interrupted even when running on a laptop on battery. It usually takes longer than 5 minutes (re timing out the lock mentioned above). -- GitHub Notification of comment by mitchellwills Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/232#issuecomment-638342121 using your GitHub account
Received on Wednesday, 3 June 2020 17:28:13 UTC