Issue metadata
Sign in to add a comment
|
Images without embedded color profile appear oversaturated
Reported by
stu...@anchev.net,
Apr 10 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Example URL: Steps to reproduce the problem: Open e.g. http://cameratico.com/tools/web-browser-color-management-test/ or any other local or web-hosted color image not tagged with a color profile. What is the expected behavior? The untagged images should appear as if tagged with sRGB profile What went wrong? The untagged imagees are oversaturated Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? No Google Chrome and Firefox (on Linux only, using Plasma desktop) Chrome version: 57.0.2987.133 Channel: stable OS Version: openSUSE Leap 42.2 Flash Version: Shockwave Flash 25.0 r0 I am using oyranos with correctly selected monitor profile. My monitor is wide-gamut and calibrated properly. In gwenview and RawTherapee I see colors correctly for all untagged images.
,
Apr 11 2017
Yes. I noticed that while testing with PageSpeed Insights: https://developers.google.com/speed/pagespeed/insights/ This tool offers for download optimized versions of the images for download. After downloading one of those images and opening it inside the browser, I noticed that it was oversaturated. Then I opened the image in Photoshop and saw that it has no color profile assigned. And this is how I found the actual issue as reported here. I am using: plasma5-desktop-5.8.6-7.1.x86_64 oyranos-0.9.5-1.6.x86_64 (with the correct color profile for my calibrated monitor) chromium-57.0.2987.133-104.6.1.x86_64 In case this matters I tried also using '--enable-color-correct-rendering' as a command line argument but the only result was that the main window didn't even show correctly - I was able to just see the title bar for a second and it disappeared instantly. So I removed that argument from my shortcut. That's all the info I have. So if you need anything further, please explain in detail how to get it for you. Thanks.
,
Apr 11 2017
Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 11 2017
ccameron@: with color correct rendering enabled, are going to handle profile-less images as if they were sRGB. If so I think shipping with the "color correct rendering" feature enabled by default will autmatically fix this.
,
Apr 11 2017
,
Apr 11 2017
Yes, exactly. There will be an about:flags to enable this in a day or two.
,
Apr 18 2017
Just tested this with "color correct rendering" enabled in about:flags, and the two rows are the same (well, up to rounding error...).
,
Apr 18 2017
,
Apr 18 2017
@ccameron: Are you testing in Plasma desktop on Linux? In about:config I have no such setting. And when running with the command line argument I still can't start Chromium.
,
Apr 19 2017
It should be available in Chrome Canary.
,
Apr 19 2017
I have just upgraded Google Chrome to 58.0.3029.81 and the issue remains. No idea if Canary version is newer. Normally I use Chromium (not Chrome) from the openSUSE official repo.
,
May 4 2017
Moving to be dupe of issue 667431 -- this hasn't launched yet.
,
Jun 12 2017
More info: The same Instagram images look different in regular and incognito modes. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by rbasuvula@chromium.org
, Apr 11 2017Labels: Needs-Feedback