PSA: Firefox beta's partially break color management

[PurdueRy]

For those of you that find this important, both the beta version of firefox and the pre-alpha are not fully .icc compliant. I noticed this after having installed the latest versions and is a big deal to me because I am using a wide color gamut monitor. Just thought I would pass on the word that if you want color management at this point...stick with version 3.

 

[foghorn67]

thanks.

 

[randomlinh]

dammit, I hope they fix that. I use FF mostly because of the same reason.. blasted wide color gamut, heh. Not that I don't like FF, but chrome's speed is just wonderful, and at home, I have plenty of ram to use up.

 

[Deadtrees]

Even on version 3, don't you have to manually turn it on by going in about:config?
Are you saying the beta version doesn't even have such options?

 

[PurdueRy]

Originally posted by: Deadtrees
Even on version 3, don't you have to manually turn it on by going in about:config?
Are you saying the beta version doesn't even have such options?

That is correct that you have to manually turn it on and specify where your display profile is located. The beta and alpha versions have the same options but the options don't work.

This is very easy for me to tell because my monitor (NEC P221W) covers 96% of Adobe RGB and this means it exceeds sRGB most notably in reds and greens. I've profiled my monitor and calibrated the internal LUTs. But if the program does not consider the gamut difference colors are inaccurate. So basically, if the browser isn't color managed everyone has a sunburn and grass glows 😉

The result I get with both the alpha and beta firefox is the same as what I get in IE(with the exception of visiting a site that tests both V2 and V4 icc profiles. Firefox beta and alpha pass v2 and fail v4). However, it appears most images online use v4 profiles because images match their IE counterpart.