Re: Last call comments on CSS3 module: color

I agree with Steven Pemberton's comments on the X11 colors (and some
of them -- "Navajo White", "Indian Red"?? -- just seem so poorly chosen).

My ideal solution would be something which isn't particularly backwards
compatible nor supporting of current implementations, but which makes
more sense to me.

Something like this:

      color: x11(SkyBlue);
      color: system(Menu);
      color: user(HyperLink);

Mark x11 support as optional (and perhaps not recommended). Only "raw"
values allowed, besides functions like these or rgba(), would be
the sixteen CSS1 color keywords, transparent, inherit, and #values.

Steven also proposed a scheme that could take keywords for
saturation, hue, etc. That could simley be something like:

      color: map(very light blue);
      color: map(slightly dark magenta-red);
      color: map(transparent cyan);

...where the map() function simply applies a mature version of the
mapping algorithm which Steven suggests at
http://www.cwi.nl/~steven/css/colour-lang.html

Oh, one more thing. Allow multiple, comma-separated color choices
such as:

      color: x11(SkyBlue), map(very light blue), #CCCCFF;

Take the first one which is understood. (A la fonts.)

--Kynn

PS:  Other color schemes could be added easily.  For example:

      color: crayon(Electric Lime), lime;
      color: crayon(Unmellow Yellow), yellow;
      color: crayon(Radical Red), #FF6666;

      ...as per Steven Pemberton's 23 May 2002 04:59:11
      message.  I'm only half-joking -- my Macintosh computer
      allows me to pick colors via crayon name.

-- 
Kynn Bartlett <kynn@idyllmtn.com>                 http://kynn.com
Chief Technologist, Idyll Mountain            http://idyllmtn.com
Next Book: Teach Yourself CSS in 24       http://cssin24hours.com
Kynn on Web Accessibility ->>          http://kynn.com/+sitepoint

Received on Thursday, 23 May 2002 16:20:04 UTC