W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2002

[CSS-TECHS] numbers instead of names?

From: Wendy A Chisholm <wendy@w3.org>
Date: Mon, 14 Jan 2002 18:23:04 -0500
Message-Id: <5.1.0.14.2.20020114180937.024720b0@localhost>
To: w3c-wai-gl@w3.org
Hello,

In relation to, "Use numbers, not names, for colors."
I'm trying to answer the question, "'red' maps to rgb(255,0,0), so what's bad about it?"

The main reason not to use color names and to use either rgb triples or hexadecimal codes is that older browsers will not recognize color names.  However, that is for specifying colors in the deprecated font element, right?

The CSS1 spec lists the following color names:
aqua, black, blue, fuchsia, gray, green, lime, maroon, navy, olive, purple, red, silver, teal, white, and yellow

HTML Source lists 140 names
http://www.htmlsource.f2s.com/stylesheets/namedcolours.html

<quote>
These are in the stylesheet section because older browsers will not recognise the words, they require the code. Any browser that can do stylesheets can do these colours, so it's safe to use them if you're using a style.
</quote>

Can anyone verify that this statement is true? If so, then we can get rid of the statement since font in HTML is deprecated and color names in CSS would be supported.

--wendy

-- 
wendy a chisholm
world wide web consortium 
web accessibility initiative
seattle, wa usa
/--
Received on Monday, 14 January 2002 18:21:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:18 GMT