W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2016

Re: [csswg-drafts] [css-color] What happens to rgb() etc with Working Color Spaces?

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Thu, 15 Sep 2016 02:40:22 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-247217812-1473907220-sysbot+gh@w3.org>
> Ah, so you're saying that rgb() is always sRGB, and it gets 
converted to the working space.

> I'm not sure that's really helpful to authors. I think they would 
prefer the defaults for all color values to be in the working space, 
including rgb() and the named colors.

> i.e. "red" should be the most reddish value in the working color 
space

Doesn't sound great to me.
- "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.
- 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.




-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/481#issuecomment-247217812 
using your GitHub account
Received on Thursday, 15 September 2016 02:40:29 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:03 UTC