Brought to you by the unholy marriage between incompatible, pre-existing standards.
You must log in or register to comment.
Got curious about this.
One notable difference between X11 and W3C is the case of “Gray” and its variants. In HTML, “Gray” is specifically reserved for the 128 triplet (50% gray) . However, in X11, “gray” was assigned to the 190 triplet (74.5%) , which is close to W3C “Silver” at 192 (75.3%) , and had “Light Gray” at 211 (83%) and “Dark Gray” at 169 (66%) counterparts. As a result, the combined CSS 3.0 color list that prevails on the web today produces “Dark Gray” as a significantly lighter tone than plain “Gray” , because “Dark Gray” was descended from X11 – for it did not exist in HTML nor CSS level 1[8] – while “Gray” was descended from HTML.
“256 Shades of Gray” could be an interesting book, nonetheless
slightlydarkerbutnottoodarkgreyis my favourite grey
Ah man, thanks for digging this up! I was always confused/annoyed by this! 🤍🩶🖤
Stuff like this is why I just used the hex color code vs the color name back in the day.
hsl is superior
oklchanyone?It doesn’t contain a labrador, but I’m open to being convinced. What’s the advantage?
it has lichs
Dude, “green” is not even close. The actual “green” is painful to look at
Could you elaborate? These are the colors that are rendered when you use the keyword I’ve listed.
Maybe I am confusing it with LaTeX
\color{green}I’m too lazy to check, tbh
