- From: Rik Cabanier via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Sep 2016 13:18:02 +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. I agree. rgb/rgba colors should be interpreted as being in the working colorspace. (Just like it happens in authoring applications.) > 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. The reason for the working color space is so you can have consistent color across devices. For instance, if an author sets the working space to sRGB, then the page will display the same everywhere (as long as the device's gamut is at least sRGB) Compositing always happens in the working color space and the end result is then mapped to the output color space. -- GitHub Notification of comment by cabanier Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/481#issuecomment-248298422 using your GitHub account
Received on Tuesday, 20 September 2016 13:18:36 UTC