srgb

The problem is that your monitor works in non-linear colourspace - sRGB, while the image is generated in linear RGB but not converted to sRGB afterwards.

If you want to show proper colours, you need to convert the final value from RGB to sRGB.

So Safari takes CSS color values assumes they are in sRGB and converts them to your display profile.

Also Firefox used the sRGB non-linear colorspace for Phong shading producing incorrect results, but it was a different annoyance.

ColorSnapper recognizes if you pick from a Color Managed App and converts the color back to sRGB.

>sRGB If we're going to be fixing colour, we can start with the abomination that is sRGB.

Multiple color gamuts—does the phone's screen actually extend well past sRGB, or did they just discover perceptual color mapping?

They calculate the Phong-model in the sRGB space but it should be calculated in a linear colorspace.

This is true in general, though for the newer MacBooks they're just getting up to a good approximation of sRGB.

Keep in mind that there is a range expansion when converting to monitor sRGB.

It has a nontrivial RGB<->sRGB conversion function and you must convert your images to/from it for every single operation like alpha blending (i.e.

The bottom line is that sRGB is hideously hard to work in.

It wasn't until Mac browsers adopted "standards" which matched the Windows way of doing things (96dpi, sRGB, MS fonts) that the Mac was really a viable web development platform.

Dell's 24" UP2414Q is an IPS 4K monitor with 99% AdobeRGB and 100% sRGB coverage, and it has a 185 PPI panel that I'd argue is already in the "retina" range.