- From: Mounir Lamouri via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jun 2019 15:03:35 +0000
- To: public-device-apis-log@w3.org
As we are adding permission plumbing into Chromium for Wake Lock, I would worry that binding wake lock and screen brightness could end up requiring some user consent for something that could be hard to describe (all the alternatives of "this application wants to keep your screen on at max brightness") and also would potentially gate the screen brightness feature behind another feature's security requirements. If we just want to expose three values, what's wrong with `screen.overrideBrightness(enum BrightnessOverride)`? -- GitHub Notification of comment by mounirlamouri Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/129#issuecomment-503599680 using your GitHub account
Received on Wednesday, 19 June 2019 15:03:41 UTC