Hacker News Reader

Comment by jzwinck | Hacker News Reader

Chrome was years behind Firefox, too: https://code.google.com/p/chromium/issues/detail?id=143 - from at least 2008 thorough 2012 there was no proper color management in Chrome, while Firefox had it. This was a deal-breaker for some users. Eventually Chrome copied what Firefox had for many years. It goes both ways.

View on HN

This is precisely the reason why I still use Firefox. It's impossible to use Chrome on wide gamut displays, everything looks oversaturated. http://cameratico.com/guides/web-browser-color-management-gu...

Chrome now supports ICC profiles for images, but still fail to color manage page elements, which is a deal breaker for me.

> no proper color management in Chrome

Can you elaborate on this? I'm relatively new at it, but I write code for a color science company so I'm curious as to what you mean.

Edit: I'm also reading halfcamerageek's URL: http://cameratico.com/guides/web-browser-color-management-gu...

Take a look at my comment below. Page elements and untagged images are rendered on the full display gamut. If you have a wide gamut display, like my 30" Dell, everything looks super saturated.

The correct behavior would be to interpret all page elements and untagged images as being in the sRGB color space. This is what the W3C recommends and Firefox follows.

The first comment on the issue is "It fails in Firefox 3 for me, working in Safari 3 though.", so the feature was copied from Safari?

Back then, you had to enable a preference in Firefox to enable full color management. For people who cared about it a lot, this was more or less OK. The commenter there probably didn't know, and you see people further down mention that. I'm not sure which browser was first to have good color management on Windows, but in any case Firefox had it within a year or so of when wider-gamut monitors started to become popular. Chrome didn't have it for about five years, and during those years I never recommended it to friends because I couldn't use it myself.

I see, I was just confused by the comment

It doesn't really go both ways. It should be expected that Chrome would be playing catchup since it launched six years after Firefox launched.

Now, as the author pointed out, Firefox seems to be unable to keep up in some key areas.

Reply on news.ycombinator.com