I won’t decide to color them blue.
I like to make users to use it when they are posting
I guess “<span class=“red”>red text</span>” is much better than"<span style=“color:#ff0000”>red text</span>" to users.
The ‘color keywords’ are limited though and not consistent amongst browsers even the WCAG suggested against using them, i.e. use numbers, not names, for colours. If you want a rough guide though what numbers “violet” may loosely equate to: http://www.w3.org/TR/css3-color/#svg-color
[font=verdana]And remember that that is a new feature in CSS3, which is a long way from being ready for deployment. In CSS1 and CSS2, the only legal colour names are the the basic 16 colours (white, black, gray, silver, blue, navy, lime, green, red, maroon, fuscia, purple, aqua, teal, yellow, olive), and that for any other colours you must use #hex or (r,g,b) codes. Most browsers will play ball with named colours, because they try to do what they think authors want, but it isn’t guaranteed.
(HTML 4, on the other hand, does allow you to use all named colours, except that you wouldn’t stoop so low as to declare a colour in HTML now, would you!)[/font]
Obviously that is why I said numbers not names as that (see link) basically was based on X11, I think Fred5 will be intending on using those CSS matches. CSS 2.1 has 17: aqua, black, blue, fuchsia, gray, green, lime, maroon, navy, olive, [orange], purple, red, silver, teal, white, and yellow. Though of course really you should avoid using those ‘keywords’ also.
The use of HTML elements and attributes for specifying colour is deprecated anyway so that usage should have stopped well over 10-years ago since the only places you could use the ‘color’ attribute was BASEFONT and FONT. LOL. The only other places you could apply colour values (keywords) being obviously: bgcolor, text, link, alink and vlink - again all deprecated for good reason. In otherwords use numbers not names.