Bug 9567 - Images without ICC profiles should be assumed to be sRGB.
: Images without ICC profiles should be assumed to be sRGB.
Status: NEW
Product: WebKit
Classification: Unclassified
Component: Images
: 417.x
: All Mac OS X 10.4
: P2 Normal
Assigned To: Nobody
http://www.reflectedspectrum.co.uk/un...
:
Depends on: 121856
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-24 14:44 PDT by Jonathan Payne
Modified: 2013-09-24 13:10 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Payne 2006-06-24 14:44:38 PDT
The standard for images on the web is sRGB, so images without an embedded profile should be assumed to be sRGB.
Comment 1 Alexey Proskuryakov 2006-06-24 16:02:13 PDT
Reporter, do you have test cases for this issue?
Comment 2 Jonathan Payne 2006-06-25 03:49:03 PDT
(In reply to comment #1)
> Reporter, do you have test cases for this issue?
> 

I've put an example as the URL. The left image has an embedded sRGB profile, whereas the right image is untagged. The untagged image should be displayed as sRGB - quoting from http://www.w3.org/TR/css3-color/ :

"the 'color-profile' property ...
auto
This is the default behavior. All colors are presumed to be defined in the sRGB color space unless a more precise embedded profile is specified within content data. For images that do have a profile built into their data, that profile is used. For images that do not have a profile, the sRGB profile is used so that the colors in these images can be kept "in synch" with the colors specified in CSS and HTML."

and from http://www.w3.org/Graphics/Color/sRGB :

"We propose that all page elements defined in the style sheets be assumed to be in the sRGB color space unless embedded ICC profiles indicate otherwise."
Comment 3 Alexey Proskuryakov 2006-06-29 04:07:00 PDT
(In reply to comment #2)

  Thank you!

> For images that do not have a profile, the sRGB profile is used so that
> the colors in these images can be kept "in synch" with the colors specified in
> CSS and HTML."

  Since WebKit does not color match the colors specified in CSS and HTML (at least not yet, though I personally find such behavior correct), this is a reason not to assume sRGB for untagged images right now.

  See also: bug 5972.
Comment 4 Pavel Perikov 2008-09-14 13:22:58 PDT
Currently we have Firefox 3.0 that does color management. Isn't it a good time to return to this bug? Vast majority of images on the Web does not include color profile information and are indeed in sRGB.  This means that WebKit users are always seeing incorrect colors except those that have their monitor color space very close to sRGB. Every MacBook user that starts Safari gets into the world of desaturated dull colors (webkit.org blogs contain many examples). People with high-end Adobe-RGB capable monitors see their images over-saturated. Many photographic sites are hardly usable (http://picasaweb.google.com/ being the prominent example)