The next version of Firefox, 3.1, is looking up to be a fairly major step up from its predecessor; it includes a variety of new features and improvements, including a new Javascript engine that is much, much faster than that of 3.0. In fact, some tests are even indicating that Firefox 3.1 can execute Javascript faster than Google Chrome (which is an accomplishment, to be sure). Other notable changes include a new tab-switching interface, and built-in support for OGG video and audio content.
However, there is another change coming, one that I believe represents a signifigant regression: enabling of color management by default. Now, in theory, this would be a good thing–after all, color management’s purpose is to compensate for differences between display devices so that color representation remains constant. Unfortunately, in my case (and, if I were to extrapolate for the purposes of this article, those of many other users) it performs quite the opposite.
On my computer, regardless of whether I’m using my monitor or the built-in LCD, turning color management on has a tendency to cause images to be rendered as if they were shining through a brownish filter. Not one to miss a beat, images that look fine on my computer are likewise rendered as brownish on other color-mangement enabled computers. Granted, that’s through no inherent fault of color management, but rather though the fact that my monitors seem to have come with faulty ICC profiles. However, the issue remains clear: if my computer came installed with a faulty profile, how many others’ computers did as well? And with that situation as it is, does it really make sense to enable color managment by default in any web browser?
0 Responses to “Color Management and Firefox 3.1”