Re: [csswg-drafts] [css-color-hdr] 2.4 "two dynamic-range-limit-mix values" should be "two or more ..." (#11694)

The CSS Working Group just discussed `https://github.com/w3c/csswg-drafts/issues/11788`, and agreed to the following:

* `RESOLVED: require strict inequality for H1 and H2`
* `RESOLUTION: allow single value, well defined`

<details><summary>The full IRC log of that discussion</summary>
&lt;ChrisL> topic: https://github.com/w3c/csswg-drafts/issues/11788<br>
&lt;ChrisL> github: https://github.com/w3c/csswg-drafts/issues/11788<br>
&lt;ChrisL> ccameron: this is to avoid a divide by zero<br>
&lt;ccameron> the epsilon should only be used to color match (very exactly) with an image<br>
&lt;ccameron> this feature is good enough without eps<br>
&lt;ccameron> it's purely numerical<br>
&lt;ccameron> can set to like 0.5 even<br>
&lt;ccameron> the epsilon value is in the gain application color space (which is linear, and is either "base image" primaries or "alternate image" primaries)<br>
&lt;ccameron> in practice, that's sRGB, P3 or Rec2020 primaries<br>
&lt;ccameron> what's the gain application color space?<br>
&lt;ccameron> primaries of the first space specified is most "normal" default<br>
&lt;ChrisL> github: https://github.com/w3c/csswg-drafts/issues/11787<br>
&lt;ChrisL> RESOLVED: require strict inequality for H1 and H2<br>
&lt;ChrisL> github: https://github.com/w3c/csswg-drafts/issues/11694<br>
&lt;ChrisL> Most edits done, need to discuss about allowing a single value or not<br>
&lt;ChrisL> agenda is https://lists.w3.org/Archives/Member/w3c-css-wg/2025AprJun/0002.html<br>
&lt;ChrisL> WPT allows single value<br>
&lt;ChrisL> agenda is https://lists.w3.org/Archives/Member/w3c-css-wg/2025AprJun/0002.html<br>
&lt;ChrisL> RESOLUTION: allow single value, well defined<br>
&lt;ccameron> https://github.com/w3c/csswg-drafts/issues/11558<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11694#issuecomment-2790760847 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:16:47 UTC