- From: Dean Jackson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Sep 2016 20:31:37 +0000
- To: public-css-archive@w3.org
> "darkolivegreen should be the most darkolivegreenish in the working color space". What's that supposed to mean? I sorta see why you'd want that for red, green, blue and possibly other fully saturated colors, but for the rest, it doesn't make much sense. The wording I used doesn't make sense for darkolivegreen. What I meant is that the values for the R, G and B primaries are taken to operate in the working color space. So it's almost certain that darkolivegreen will produce a different color when the working space is sRGB as opposed to P3. If we don't do it this way, I'm not sure what the point of the working color space is, because all your #rrggbb, named colors, rgb() values are unchanged. > This would be error prone and author hostile. Changing the color space of your previously perfectly working page in order to do some new things that call for a bigger gamut mean that you'd need to redefine all the colors in your page, or they'll end up different. Exactly! The alternative is to manually change all the color rules to be in the working color space. Note that you don't necessarily have to set the working space to "do some new things that call for a bigger gamut". After all, that's exactly what we're doing today without this working color space feature. -- GitHub Notification of comment by grorg Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/481#issuecomment-247702069 using your GitHub account
Received on Friday, 16 September 2016 20:31:58 UTC