W3C home > Mailing lists > Public > www-style@w3.org > September 2010

Re: [css4-color] @color Custom Color Keywords

From: Christoph Päper <christoph.paeper@crissov.de>
Date: Mon, 20 Sep 2010 10:34:54 +0200
Message-Id: <FA827F63-0917-4CA8-AB90-FD42E46D2B64@crissov.de>
To: www-style list <www-style@w3.org>
Tab Atkins Jr.:
> @page isn't a variable mechanism at all;

On its own it’s not, in combination with the ‘page’ property it kind of is.

> Reusing existing color keywords is probably a bad idea in general.

It is a bad idea for some reasons and it is a good idea for other reasons. I think the latter outweigh the former, you obviously don’t.

> It would be confusing if "color:darkred" meant something in one stylesheet, and a different thing in another stylesheet.  

What’s the difference to “font-family: Helvetica” (or “font-family: serif”)?

> It's not expected that that expression can be mutable,

It’s expected that ‘darkred’ yields a dark red, not that it actually results in exactly the same color as ‘#8B0000’ or ‘rgb(55%, 0%, 0%)’. Also, expectations change all the time.

> I mean that I don't think new ways to express a <color> value will occur often.

Sorry, I’m still not sure I understand what you mean. Do you believe color variables won’t be used often or do you believe HSL etc. won’t be used often or do you believe color scoping wouldn’t be used often?

> A color is a color; it acts the same everywhere.

‘currentColor’ and possibly system colors don’t. (Well, it /acts/ the same, but doesn’t /look/ the same everywhere.)
Received on Monday, 20 September 2010 08:35:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:49:47 UTC