Posted by Jeff Lewis on February 12, 2013 at 2:29 PM
While working through posting some photos I was happy to see that as of Sep 2012 or so Chrome finally got color management for image display, but it looks like it's a little off from what IE9 does for me.
Basically, if you embed a color profile, like sRGB, for me Chrome's display is slightly less saturated and darker than (reduced gamma?) than IE9's display with or without a color profile, and Chrome's display without the color profile.
So it seems like if you want consistent display across both browsers you need to post your images as sRGB WITHOUT the embedded profile.
Just wondering if this is just happening for me, or a known issue and everyone just strips the sRGB profile from their images, or it's more important to leave the profile in despite the display inconsistencies.
Posted by Richard Ditch on February 12, 2013 at 2:54 PM
All my images are posted in sRGB and I embed the sRGB profile in every image I post on the web. That seems the best way to ensure my images look correct to the greatest number of viewers. But I can't be responsible for the settings on every computer used to view my images and I don't waste energy worrying about it.
As a Mac user I am used to color aware applications and browsers (Safari, and now Firefox). Checking Chrome on my Mac - your Short-eared Owl in flight looks the same in Chrome as it does in Safari and Firefox.
Posted by Mark Stahlke on February 12, 2013 at 3:12 PM
What version of Chrome are you using?
Posted by Jeff Lewis on February 12, 2013 at 3:36 PM
Ah yes, I should have clarified my PC-centric post, for me this is on Windows7. And I just checked Firefox as well and interestingly it's showing the same behavior - embedded sRGB makes it slightly darker and less saturated, and no embedded makes it look the same as it does most other places - IE9, in Photoshop, in Quicktime viewer, in Picasa, in Windows Paint.
Since Chrome + Firefox from Windows PCs together are very possibly 75%-85% of the browser accesses to any photographer's site, I was just wondering if this was an issue anyone was worrying about. And the reason I noticed is that I'm working on an eagle shot I have, and noticed that the underwing shadow detail I worked at preserving got completely crushed away when I looked at it in Chrome with the embedded sRGB, and when I stripped the profile it came back.
Posted by Jeff Lewis on February 12, 2013 at 3:39 PM
Mark, my version is 24.x on a PC, and it looks like it got color management as of 22.x
Discussion
4 repliesBasically, if you embed a color profile, like sRGB, for me Chrome's display is slightly less saturated and darker than (reduced gamma?) than IE9's display with or without a color profile, and Chrome's display without the color profile.
So it seems like if you want consistent display across both browsers you need to post your images as sRGB WITHOUT the embedded profile.
Just wondering if this is just happening for me, or a known issue and everyone just strips the sRGB profile from their images, or it's more important to leave the profile in despite the display inconsistencies.
There's a nice test site for all this at http://regex.info/blog/photo-tech/color-spaces-page2
thanks,
Jeff
As a Mac user I am used to color aware applications and browsers (Safari, and now Firefox). Checking Chrome on my Mac - your Short-eared Owl in flight looks the same in Chrome as it does in Safari and Firefox.
Since Chrome + Firefox from Windows PCs together are very possibly 75%-85% of the browser accesses to any photographer's site, I was just wondering if this was an issue anyone was worrying about. And the reason I noticed is that I'm working on an eagle shot I have, and noticed that the underwing shadow detail I worked at preserving got completely crushed away when I looked at it in Chrome with the embedded sRGB, and when I stripped the profile it came back.