- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jul 2020 00:14:25 +0000
- To: public-device-apis-log@w3.org
It sounds like what you are seeing is based on Chrome's implementation, which happens to be holding the lock at a particularly brightness without allowing it do dim - so I'm hoping to hear from the Chrome folks, as I'm not sure who implemented the feature. Personally, if I was to do this in Firefox, I would only do "full" and "auto" (or default). However, I'm certainly open to this third state: To reiterate what we have so far: * default: use the current brightness, and (if possible) *don't allow the screen to dim* - (OSs power settings probably override this). * auto: use the current brightness, but let the OS do whatever it wants with regards to dimming. * full: request full brightness, and let the OS do whatever it wants. When I say "use the current brightness", the user is still obviously in control and can adjust it. Similarly, in all cases, the OS can do whatever it wants/needs to do based on available battery: the browser shouldn't override the OS, IMO. As I said, I'm remain skeptical that "default" and "auto" are different (it sounds like an implementation detail of Chrome) - but I'm open to listen to reason as I've not implemented this Firefox yet. -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/129#issuecomment-665357952 using your GitHub account
Received on Wednesday, 29 July 2020 00:14:27 UTC