- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Aug 2022 14:53:49 +0000
- To: public-css-archive@w3.org
> @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. (the benefits being that values round trip cleanly and that you can use things like out of gamut color(srgb ...) to express things like Display-P3 colors, which is a common practice in Apple's graphics stack these days). > > Ultimately, if the spec authors think this behavior is preferable, this is an easy thing for us to implement (we used to do a clamping gamut mapping here after all, I could just plug in the CSS Gamut Mapping algorithm instead) and I will be happy to. I do not think that's preferable at all, moving a window to another screen with a different gamut should not cause the computed style of colors to change! @svgeesus will do some digging on why this changed, since he also doesn't think it's a good idea. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7610#issuecomment-1225837632 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 August 2022 14:53:51 UTC