Our designer was pissed off when we discovered this bug, which explained why Chrome was the only program that displayed RGB values differently from all the others (not just browsers). She'd been careful about standardizing and tweaking colors we already used to work better for people with colorblindness, much of which was thrown out the window on Chrome. Not to mention issues matching the PNGs and SVGs she created for the site.
Quick edit:
> Why so much resistance?
Comment 34:
> Chromium developers have previously stated this won't be supported for reasons mentioned in this old post.
> https://www.webkit.org/blog/73/color-spaces/
From that link (posted in 2006):
> The big hurdle that we ran into, though, was with the drawing we did not control, namely the Flash plug-in. The problem is that designers specify colors in Flash and colors in CSS in the Web page, and they expect those colors to match. Because Flash’s drawing isn’t correcting to sRGB, if we did it in Safari, there would be color mismatches all over the place. These mismatches look far worse than if we just don’t correct at all.
Isn't Flash gone from Chrom(ium) now?
Wow. Just wow. I have rarely seen so much ignorance. And this exactly why Chrome is cancer for the whole internet. I mean, seriously, why should the web developers fix something that is standardized just to make it work in Chrome? And fixing the JPEG standard...?
"We're not doing as the spec tells us to, BUT that probably gives us performance gains, most users don't care about it anyway, I prefer it that way, webdevs should fix it, we should fix the JPEG standard instead (!?)..."
Why so much resistance?