On 30 Mar 2007, at 12:05:07, Mauricio Samy Silva wrote: > If you specified a color name (one of the 17 valid colors keywords > on the > Specs) browsers can render > it slightly different (i.e. red (or other color name) is more ou > less darken > according the browser). > This can "broken" the contrast the same way as: > #008083 provides a good contrast over #fff > and > #099 (slightly different from #008083) doesn't provide sufficient > contrast. > > In my opinion, if I'm not missing something, the main point is > #008083 (or > other valid number color) is the same in all browsers and gray (or > one of > the 17 valid colors keywords on the Specs) isn't the same across > browsers. > > Number color CSS value is consistent across browsers and colour values > isn't.
No, the CSS 2.1 spec explicitly states what the hex values for the colour names are: <http://www.w3.org/TR/CSS21/syndata.html#value-def-color> So, for example, "teal" is defined as being synonymous with "#008080", and any browser which rendered it using a different value is by definition broken. Incidentally, the "gray"/"grey" issue isn't helped by the fact that Netscape Navigator had an extensive list of colour names, which included both "gray" and "lightgrey" - the story I heard back in the day was that an English developer had been involved in implementing that bit of code, and automatically used the English spelling. As a result, browsers nowadays support both "lightgrey" and "lightgray" for backwards compatibility... although none of those extended colour names appear in any formal spec relating to CSS, so that's OT. Regards, Nick. -- Nick Fitzsimons http://www.nickfitz.co.uk/ ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7 information -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
