- From: Eli Grey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Jul 2022 03:35:19 +0000
- To: public-device-apis-log@w3.org
> Non-LCD display (e.g., CRT and OLED) can cause screen burn if the brighter pixels are continually lit. However it is technically difficult for browsers and OS to identify the type of display, making it difficult to resolve the problem. This is already handled by display drivers in current displays. Some older OLED displays (and most CRT displays) don't have this functionality, but modern OLED displays will automatically dim and pixel-shift to prevent burn in when the driver detects that the display is being driven at a high brightness for too long. Similarly, LCD devices implement similar solutions to dim their backlights upon reaching thermal constraints. Again, I don't think brightness control should be a gated permission, but I do think it should be scoped to web-controlled render surfaces. Unfortunately this necessitates an implementation exclusive to HDR-supporting devices. Fortunately "HDR-supporting devices" includes most OLED phones newer than the Galaxy S5 from 8 years ago. -- GitHub Notification of comment by eligrey Please view or discuss this issue at https://github.com/w3c/screen-wake-lock/issues/335#issuecomment-1177014765 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 July 2022 03:35:20 UTC