- From: Chris Cook via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Sep 2021 11:10:04 +0000
- To: public-css-archive@w3.org
That's a great point. I also started building websites in notepad (without the ++), so can relate with the desire for minimal build tools. I don't have any authority to say whether this should be in the spec or not, but I do feel like there are plenty of alternatives to get kelvin colours on a webpage. The burden of putting this in the spec is that every browser then needs to go out and build it, we hope they all get it right, and then if they either don't all implement it, or don't all do the same thing, we end up with a very hard to use feature. One other concern I can see (I'm not sure whether this is either a non-issue or has already been solved, so I'm interested to find out) is that CCT is an absolute colour description. In sRGB, 6500 kelvin is essentially [1,1,1], but in another colour space (one with a white-point of D50, for example), the same 6500 kelvin has now changed 'colour', it would now be represented as something more blue than [1,1,1]. This might not be an issue if we always assume browsers are displaying colours with a D65 white point, but that might not be ideal. Again, I don't know enough about the existing and planned specs to know if this is actually an issue, so keen to hear what others think. -- GitHub Notification of comment by Smilebags Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6582#issuecomment-916823113 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 September 2021 11:10:06 UTC