It sounds like you have a wide-gamut monitor.
I don't think there is much you can do right now except use FireFox.
Here is a link to the bug report for Chromium that you might find interesting. I think it gives some insight into the situation.
http://code.google.com …um/issues/detail?id=37028
I think there are a few problems/situations that slow the possibility of a "fix" from the Chrome team:
* Google isn't much into switches and mass configurability to its software. The Google strategy is more to create a slick, standard interface and not complicate things.
* In the past, there has been some controversy regarding whether assuming sRGB for untagged images is the way to go. I don't believe that there is any color-managed browser yet that applies color management to non-image graphical elements. That means that if a web developer wants an image to match color with non-image graphical elements on the page, the only way for them to do that is with untagged images. When the browser assumes sRGB for the images, that can make image and non-image colors to no longer match or mix in the same way. That is probably a minor deal for you and me but it can drive web designers and marketing departments nuts.
There may be hope, however. Apple finally made Safari on the Mac assume sRGB for untagged images (I believe that the latest version of Safari for Windows still does not). That surprised me given how much Apple caters to the web development community but maybe that move will help convince Google to do something similar.
* Color management, in general, takes a back seat for these browser development teams. Serious photographers make up a relatively small portion of the user base as a whole and the wide-gamut monitor owner segment is smaller yet. Bug fixes and new features that impact the bulk of the user base are going to get more attention and priority. That may change as wide-gamut monitors become more prominent.
Color management functionality also seems to always cause some amount of performance penalty in the browser. Since browser makers get mileage out of being able to say their browser is the fastest, this is another reason that color management tends to get sent to the back burner. I think all we can do is try to make our voices heard and let them know that browsers are fast enough now that speed can be moved down the priority list to favor other features like color management.
Another factor that I think MAY play a role is general ignorance on browser development teams with respect to color management. It is kind of a specialty knowledge area and one that requires a certain amount of study and experience. It is also an area that can get kind of complicated. It has a rather nasty mix of physics, biology (how humans perceive the physics), and software implementation. Because of that mix, compromises often have to be made and those compromises involve subjective decisions (satisfy all the people some of the time or some of the people all the time?).
But I bet there's a lot of folks that post that have no idea how horrible their images look to someone using Chrome with a wide gamut monitor, and even more using Chrome not understanding the issue.
