(chromium-dev in bcc)
I went down the rabbit hole of several color management related issues, and came out believing there's a lot of confusion and misunderstandings in those (very long) threads, which IMO need sorting out.
So, I'll try to sum up the state of affairs here:
1) CSS Color management
CSS colors are sRGB, and in order to be accurately displayed on screen with non-sRGB color profile, need to be color corrected before sent to screen.
Currently in Chrome
and Firefox* that is not the case, but it is the case in Safari. There have been past claims
that color managing CSS will break content, but from Safari supporting it, one can assume that it is fairly safe to do so.
2) Image color management
Images that contain an ICC profile seem to be properly handled on desktop Chrome, but not so on Android
One can also argue that it is also important for color consistency to make sure that images and CSS colors are in the same color space, even if means that the colors are not accurate. Taking this approach means sending sRGB color profiles along with all images (even ones that are using the sRGB color space), which is extremely wasteful. Facebook seems to be taking
OTOH, for images, there probably would be some perf costs when color space conversions are required.
3) Video color management
More or less the same as images, but performance impact may be more significant.
All in all, it seems like everyone would be better off if in the case of non-sRGB display, CSS colors, as well as images and video with no color profile would all be assumed sRGB and color corrected to the display's color space rather than sent to it as is, leading to color inconsistency between devices. Also, fixes for all these issues have to be shipped at the same time, to avoid color inconsistency between images and CSS colors.
The downsides of fixing these issues are a potential compatibility risk (which the Safari experience may suggest is a non-issue) and a potential performance hit for the users that need this color correction (assuming we can avoid color correcting for sRGB display users).
What do you folks think? Did I cover the full breadth of these color management issues correctly?
If so, should we try and fix these issues despite the perceived risks?
* Firefox enables users to turn on color management using a flag. However that flag is off by default.