4 ms·
I understand the arguments against this, but I don't think I've ever met a web developer that actually still uses the color names. I saw it often in 2007 or so,
by toxican 11y ago
I understand the arguments against this, but I don't think I've ever met a web developer that actually still uses the color names. I saw it often in 2007 or so, but not at all anymore. So I'm left not really caring about a slippery slope of names appearing in a list of things nobody uses.
And I should say that despite color names not really being used, it's still a very nice gesture.
- patja 11y agoThey are a nice transitional crutch for students just getting started. I teach html, css, and javascript to 13 year olds using Adobe Brackets. The color name code completion is a big assist early on when introducing the basics of CSS before getting into the more daunting hex codes or RGBA values.
- toxican 11y agoAgreed. That's the last time that I used them. Then I branched into #ffffff, #000000, learned how the shorthand hex codes worked, etc. They don't really have a place in a professional environment though, so adding a new on as a tribute doesn't really harm anything at all, imo.
- duskwuff 11y agoThe color list is already ridiculously large anyway -- early web browsers allowed color names to be used from the X11 "rgb.txt" [1], bringing us colors like "papayawhip", "firebrick", and (as mentioned below) "peru". So it's not as though adding one more color is some sort of huge burden. [1]: http://en.wikipedia.org/wiki/X11_color_names http://en.wikipedia.org/wiki/X11_color_names