Issue metadata
Sign in to add a comment
|
chrome 62/63: color rendering is different from 61 |
||||||||||||||||||||||
Issue descriptionChrome Version: 62.0.3202.38, 63.0.3229.0 OS: Win7 What steps will reproduce the problem? Open a color test image, e.g. http://www.imagingassociates.com.au/color/images/test-patterns/EBU_ColorBars-768x576.png, and compare color rendering in chrome 62/63 vs chrome 61. What is the expected result? Same colors in chrome 62/63 and 61 What happens instead? Colors are not the same. See attached screenshot (sidebyside_62vs61a.png) with rgb values in different areas. Other details: - The issue affects video rendering as well (try any color test video on youtube); - It seems only affects Windows. No issue on Linux.
,
Oct 3 2017
Unable to reproduce the issue on reported version 62.0.3202.38, 63.0.3229.0 on latest canary 63.0.3230.0, latest stable 61.0.3163.91. Attaching screenshot for reference This issue seems to be related to color correct rendering specific profile hence, requesting ccameron to please have a look into the issue as we are unable to reproduce the issue from TE-end
,
Oct 3 2017
Please attach the ICC profile from this machine.
,
Oct 4 2017
Just to verify, are you running Win7 when trying to reproduce? As far as I know, this bug is Win7 only.
,
Oct 4 2017
The .icm profile that you have installed instructs Chrome to use the colors that you are observing in Chrome 62. In particular, for the blue bar: - the image specifies sRGB colors of 0,0,191 - that sRGB color, transformed to the TPFLX60.icm space is 57,0,183 So, this is behaving as intended. I'm surprised that Chrome 61 was different (did you disable color correct rendering)? If you don't like the colors with this profile, then you should uninstall it.
,
Oct 5 2017
@ccameron, I've observed this problem of the washed out colors on chrome 62/63 but not on chrome 61 across several systems, so I still think something is amiss, here. When did color correct rendering become the default? If I'm still seeing this on systems with color correct enabled and getting different behavior across 61 and 62/63, what information would be helpful to you to track down the problem?
,
Oct 5 2017
Colors appear "washed out" when you use a wide color gamut color profile. If you don't want to use a wide color gamut profile, please uninstall it from your system.
,
Oct 5 2017
When did color correct rendering become the default? I'm noticing this on a large number of systems, and these are systems where the users have not knowingly gone out of their way to customize their color profile. I understand your position is "those users should just uninstall the color profile that they don't like", but as I mentioned, these users did not knowingly set their color profile, so they will have no idea they need to uninstall something in order to fix it. From the users perspective, Firefox will just mysteriously provide a more vibrant color experience.
,
Oct 5 2017
This has always been enabled for some content (inconsistently). In Chrome 61, it is applied to all content. If you want to disable this, you can disable "color correct rendering" in about:flags in Chrome 61. In Chrome 62, you can do the same thing by setting "force color profile" to sRGB in about:flags. If you do this, then you won't see any wide color gamut images, FWIW.
,
Oct 9 2017
I've attached a color profile (and screenshot) from a system where colors look far more faded in Canary compared to Chrome 61 and Firefox. Is this also a wide-gamut profile?
Again, this user didn't explicitly or knowingly change their color profile, this is what happened to be installed and activated on their system. From this user's perspective, Firefox just provides a more vibrant color experience for some mysterious reasons that can never be understood or changed ("normal" users don't go into chrome://flags and are not really encouraged to).
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Oct 2 2017