- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Aug 2022 15:22:07 +0000
- To: public-css-archive@w3.org
> Following the spec on this point would make the result of gamut mapping visible via getComputedStyle(element). Do you think the spec should change on this point? > Oh, very interesting. I don't believe that was in the spec when I was last working on this (I made an intentional change to match the spec and to not clamp around a year ago if I remember correctly), so thank you for bringing this to my attention. > @svgeesus @LeaVerou, what was the driving motivation behind this change? To me, it has some unfortunate downsides, and I am not clear what you gain from it over the (or perhaps just my) previous interpretation which was that out-of-gamut colors would be preserved all the way to use time. My recollection is that CSSWG went back and forth on this, between computed value time and used value time; and the main driver was handling system colors in forced color mode, and handling currentColor. I think that mapping to the display gamut should be as late as possible, so that out of gamut values like `rgb(100% 100% -34.627%)` (which is `color(display-p3 1 1 0)`) round-trip cleanly, preserving author intent. I would need to dig into the commit history to see when that was changed and in response to what issue, but from memory it was to do with handling system colors. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7610#issuecomment-1219626633 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 August 2022 15:22:09 UTC