- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jul 2020 00:36:53 +0000
- To: public-device-apis-log@w3.org
I'm sorry for not engaging on this issue earlier. Thank you for filling in the details on the use cases. What Chrome implements today is what @marcoscaceres proposes as "default". I am supportive of a "full" option for the QR code use case. In the use case for "auto" is dimming while keeping the device unlocked the desired behavior or is it sufficient to enable the site to continue to run while the display is off? If that's the case then it seems like a use case for the [System Wake Lock API](https://github.com/w3c/system-wake-lock) as a "dimming okay" version of this API would use more power keeping the display lit than the application requires. I think the difference between "default" and "auto" as proposed is significant, as dimming the screen reduces the visibility of the content being displayed and the intent of the API is to allow the content to remain visible. -- GitHub Notification of comment by reillyeon Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/129#issuecomment-665364294 using your GitHub account
Received on Wednesday, 29 July 2020 00:36:54 UTC