- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Apr 2025 19:27:16 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `https://github.com/w3c/csswg-drafts/issues/11558`. <details><summary>The full IRC log of that discussion</summary> <jyasskin> topic: https://github.com/w3c/csswg-drafts/issues/11558<br> <ChrisL> github: https://github.com/w3c/csswg-drafts/issues/11558<br> <jyasskin> ccameron: We probably won't agree on the default value. Having auto be browser-chosen and map to a single value .. maybe it's start on one state, and we'll eventually agree on something and be able to standardize that.<br> <jyasskin> ccameron: But I think I can't change several years of Chrome behavior, and good HDR doesn't need reduction, and the concern that HDR content will get mastered poorly if constrained by default.<br> <jyasskin> ccameron: I think we should have auto do what the browser wants, and provide the signal that the user left the default instead of explicitly asking for one of the options. Is that reasonable?<br> <jyasskin> simon: Apple doesn't hav etoo much information. We want auto to be uniform for all elements. Ideally we don't want images+videos to have different behavior if 'auto' is applied to both, but we have historical behavior we might have to support.<br> <jyasskin> simon: Can't commit that auto will be the same for all elements. Don't want heuristics ... might decide full-screen will allow full HDR.<br> <jyasskin> simon: Don't plan any in-page heuristics like "image is next to text".<br> <jyasskin> simon: Question about HDR-css colors vs HDR images & video: are we agreed that the dynamic-range-limit property affects both box decorations and content?<br> <jyasskin> <yes><br> <jyasskin> ChrisL: We don't have syntax, and we're waiting for someone to do it, but we intend it to affect everything. If you want a particular thing, you should select it.<br> <jyasskin> simon: We do have a bug, but that's a bug. When people start specifying these colors, people might want to specify colors and replaced content separately.<br> <jyasskin> ccameron: Can specify different colors for different elements.<br> <jyasskin> simon: Videos have internal controls (??) which might want different color limits.<br> <jyasskin> ChrisL: I'm writing some tests.<br> <jyasskin> ChrisL: WPT is SDR & sRGB-only, but you can still test color mapping. Don't know how you'll get a headroom value.<br> <jyasskin> ChrisL: Does Apple have concerns?<br> <jyasskin> simon: Haven't digested the spec enough. Any concerns would be in terms of how HDR colors coexist with other content. To prevent annoying use.<br> <ccameron> proposed resolution: add "auto" value, which maps to browser-defined value (1 of the 3)<br> <jyasskin> ccameron: Suggest we sleep on this.<br> <jyasskin> simon: Think I'm ok resolving to add an 'auto' value, but not ready to say exactly how it behaves. Not ready to say it applies equally to images and video.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11558#issuecomment-2790782546 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 April 2025 19:27:17 UTC