"Steve Swift" <St***********@gmail.comwrote in message
news:46******@news.greennet.net...
>That's irrelevant to the question about "HTML safe colors". If you use a
color that is not one of the colors supported by a display device, it
will be mapped to the nearest supported color. So what's the problem?
The original problem was that if you used an "unsafe" colour some
combinations of browser/display adapter tried to display the colour by
using a dithering technique which resulted in some weird-looking patterns
appearing.
Nope. The original problem was with images, at the time gifs. A gif has a
256 colour palette and if there are more than one of them on a page then the
different colours in each of their palettes would add up to more than the
256 colours that 8 bit colour cards could handle.
The first gif would display correctly as each of its colours (well most of
them, as there are only 240 colours available) would map into an empty
palette register. But each subsequent gif would be limited to those colours
that had already been loaded.
Paint a nice sunset in varying shades of red and pink, use up the palette,
your next gif of a blue and green ocean would be trashed.
The browsers did not do any dithering, ever. Nor did the hardware. It was
merely a lack of available colours in the palette. A hardware problem. I
wrote an article about this in the 90's. Must dig it up.
I would doubt that this is much of a problem any longer.
No, its no longer a problem. And, in fact it was and sometimes still is
detrimental. The "colour safe" colours do *not* map into a 16 bit colour
space. There was a while there when all sorts of artefacts appeared, image
background colours not matching with the page background and so on. I wonder
if some of these new telephones have 16 bit colour?
Someone with a 256 colour display probably doesn't matter much anyway.
:-)
And they are used to seeing green people :-)
--
Richard.