- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jul 2020 23:15:58 +0000
- To: public-device-apis-log@w3.org
> > 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. > > Agree. I guess the question I have is if it's feasible to implement "default" (no dim) across all OSs? My assumption is that the browser can only request from the OS to keep the screen on (but OS manages what happens), or keep screen on with "full" temporarily (but the OS still manages everything). Is that understanding correct based on what @kenchris documented above? [#129 (comment)](https://github.com/w3c/screen-wake-lock/issues/129#issuecomment-479882316) From the Android API it seems like BRIGHTNESS_OVERRIDE_NONE corresponds to "default" and using BRIGHTNESS_OVERRIDE_FULL would be how to implement "full". If we wanted to implement a "dim" option as well then BRIGHTNESS_OVERRIDE_OFF would be the solution. > I think there's more to allowing full screen brightness than a few individual use cases. I would say that from an accessibility point of view that's a no go. Users set a preferred fixed brightness or an auto brightness in the OS. They expect that to happen. For instance, in a dark environment users expect their fixed brightness set by themselves, or a low brightness set by the OS (that's what auto does). They don't expect apps shooting a full-glare brightness at them at night. I would argue that allowing an app to request full brightness is similar to allowing an app to request full sound volume. I agree this is something to consider before implementing a full brightness mode. My understanding of the use case is that app developers don't expect users to know how to adjust brightness when they are displaying something like a barcode. To support this case it seems sufficient for the site to provide a hint that full brightness is suggested and the browser can provide the UI to enable it if the user desires. -- GitHub Notification of comment by reillyeon Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/129#issuecomment-665978015 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 July 2020 23:16:00 UTC