- From: Christopher Cameron via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Feb 2025 04:55:16 +0000
- To: public-css-archive@w3.org
I'm sympathetic to the idea that if we were coming at this ex novo, having `standard` as the default would be reasonable. That said, we're opposed to this. > Re: simplicity Having `video` and `img` behave differently will probably be long-term confusing. The only way to explain that behavior is to reference historical behavior. > I believe Chrome does support HDR images in some capacity already, so this would be a change for them. Chromium has supported HDR images for >3 years, and there are partners, products (Google Photos), and now there are unrelated out on the web pages (especially in the photography area) that support this. > Re: CSS color If we allow something like `color(srgb 10 0 0)` to be HDR by default, then we have to answer the question of "what is the default tone mapping for this color to SDR, to 2x headroom, etc", which I think makes things more complicated. Requiring use of `color-hdr` to get HDR color makes it so that adding an HDR color requires also specifying how the color should look in SDR, which avoids this problem. It also makes implementation much more complicated. The user agent needs to "turn on HDR" based on the content that is on-screen. In particular, it needs to configure its display to have some amount of headroom (headroom isn't free in terms of memory and power). It's easy to detect HDR images or videos, because they're marked as such (and they also include metadata indicating how much headroom they need). But for individual colors, is the color `color(srgb 1.2 0 0)` supposed to be HDR? Maybe? But it's equivalent to `color(rec2020 0.99 0.30 0.11)`, so maybe it's just wide-gamut SDR. The `color-hdr` syntax makes it clear (1) when a color is to be HDR vs not (2) the maximum HDR headroom it will use. -- GitHub Notification of comment by ccameron-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11711#issuecomment-2686913501 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 February 2025 04:55:17 UTC