- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Nov 2018 03:32:05 +0000
- To: public-device-apis-log@w3.org
There's a small risk of DoS if we let sites reduce the screen brightness, since users might not then be able to see the screen well enough to undo it. A separate API could, of course, deal with that risk, perhaps by forbidding sites from decreasing the brightness, or by showing a different prompt if the brightness is going down from when it's increasing. Even after the Extensible Web Manifesto, we sometimes decide to provide a high-level API if it means the permission prompt can be simpler. This doesn't prevent us from *also* providing the low-level API with a scarier permission prompt. So, what would the permission prompt look like for the brightness-setting API? Is it as acceptable to ask for forgiveness in that case as it is for wake-locks, given the concern above? Will the extra complexity in defending against DoS slow down implementation of the lower-level API, when we might be able to get the wake-lock version sooner? -- GitHub Notification of comment by jyasskin Please view or discuss this issue at https://github.com/w3c/wake-lock/issues/129#issuecomment-440125471 using your GitHub account
Received on Tuesday, 20 November 2018 03:32:06 UTC