Re:“Tomato” versus “#FF6347” – the tragicomic history of CSS...
by caf on Thursday October 15, 2015 @07:28PM
(#10396631)
If you were writing an application where you wanted to allow your user to choose colours - say for tagging items or customising an interface - it might make sense to present them with a list of named colours rather than make them choose from a colour wheel (or, heaven forfend, directly enter a 24 bit RGB number).
It would likely be best to define your own list of named colours, for localisation reasons if nothing else, but for the initial version of a feature I could see using the CSS colour names directly.
Re:“Tomato” versus “#FF6347” – the tragicomic history of CSS...
by wavefunction on Thursday October 15, 2015 @04:13PM
(#10395671)
I use the hex-values/rgba because what does 'papaya whip' even mean? Plus not everyone on the internet are literate in English so RGBA or hex-RGB is far more internationalized.
Re:“Tomato” versus “#FF6347” – the tragicomic history of CSS...
by thaumasiotes on Thursday October 15, 2015 @06:46PM
(#10396469)
> “I'm not a native English speaker. Imagine my reaction the first time I saw the ‘gainsboro’ color or ‘papaya whip,’” Daniel Glazman, co-chairman of the CSS Working Group, told Ars.
Speaking as a native English speaker, I don't see how this could possibly be worse for non-native speakers. They have no idea, and neither do we.
I'd rather just use the hex value and ensure it's rendered even if the browser hasn't implemented the latest version of the spec.