Re: [csswg-drafts] [css-color] How to handle out-of-bounds legacy srgb values? (#10087)

The CSS Working Group just discussed `[css-color] How to handle out-of-bounds legacy srgb values?`.

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> i/Subtopic: /fantasai: Let's take back to the issue or lunch break/<br>
&lt;ChrisL> Proposed Resolution: out-of-bounds legacy srgb values are clamped at computed-value time<br>
&lt;fantasai> ChrisL: oriol's suggestion<br>
&lt;fantasai> fserb is nodding<br>
&lt;emilio> q+<br>
&lt;fantasai> emilio: does this match implementations? I think it doesn't<br>
&lt;fantasai> emilio: seems fine-ish<br>
&lt;fantasai> emilio: but I thought implementations were fairly interoperable here<br>
&lt;fantasai> oriol: in the tests I have, I was producing this legacy rgb colors using animations with custom timing function that could force one of the children to become negative<br>
&lt;fantasai> oriol: what I saw was that webkit clamps at computed value time, but Blink and Gecko did not<br>
&lt;fantasai> oriol: so child would inherit value that's out of bounds<br>
&lt;fantasai> oriol: if you serialize the color hten it gets clamped<br>
&lt;fantasai> oriol: if you reassign the serialization then ??<br>
&lt;fantasai> dbaron: This is proposing that they are clamped at computed value time in addition to any clamping at parse time<br>
&lt;dbaron> s/parse time/parse time?/<br>
&lt;dbaron> ChrisL: yes<br>
&lt;emilio> q+<br>
&lt;oriol> s/??/it doesn't really round-trip on children that are inheriting/<br>
&lt;fantasai> emilio:<br>
&lt;fantasai> emilio: color-mix() not being able to represent animations is a problem<br>
&lt;fantasai> emilio: otherwise you can't express currentcolor in the computed value properly<br>
&lt;fantasai> emilio: we should maybe revisit this, which may change the resolution here<br>
&lt;fantasai> ChrisL: Let's take it back to the issue then<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10087#issuecomment-2162785631 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 12 June 2024 11:35:28 UTC