Colors randomly rendered incorrectly (or some sort of color profile applied)
Reported by
teo8...@gmail.com,
Aug 26
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Example URL: https://www.facebook.com/ Steps to reproduce the problem: Some time ago I noticed what I thought to be a change in Facebook's blue background color. At that time that's the only place where I noticed it, and I assumed Facebook had changed it. I didn't inspect the CSS or html but I did take a screenshot. A few days later the color went back to normal and I assumed again Facebook had been trying out changes in their style. I took another screenshot of the same piece of blue background, which now looked like it used too. Then it happened again a few days ago and I realised that similarly blueish colors were different than usual in other websites too, and even in the traditional (and default) "electric blue" used to highlight links in many websites. So this was not at all a Facebook thing. So this time I went and inspected the html and CSS in Facebook. The rgb() color specified in the CSS didn't match the rendered color. The way I checked this was: - I took a screenshot - I opened the screenshot in GIMP - I used the color picker to get the color of a pixel and looked at the RGB values of the actual color. They didn't match those specified in the CSS property. And there was no image nor transparency involved. I started fearing that some color-profile setting in my OS for the screen had gone berserk. However: A few minutes ago, the colors went back to what they used to be, in front of my eyes, meaning I witnessed the moment where the colors changed and went back to usual. There I was able to confirm that, definitely, everything outside Chrome remained unchanged, while the changed affected other websites besides Facebook. See the attached screenshots. What is the expected behavior? What went wrong? ... Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? Yes Does this work in other browsers? N/A Chrome version: 68.0.3440.106 Channel: stable OS Version: Flash Version:
,
Aug 26
,
Aug 27
Unable to reproduce the issue on reported chrome version #68.0.3440.106, using Ubuntu 17.10 by following below steps. Steps: ====== 1.Launched chrome. 2.Navigated to facebook.com, observed the site appeared in the normal blue color(the usually way it gets displayed). Note: Tried with Dual monitor setup using Mac Os 10.13.3 as primary and Ubuntu 17.10 as secondary moniter, but unable to reprduce the issue. Attached screenshots for reference. @Reporter: Could you please review the attached screen-cast and confirm if anything being missed here and request you to retry this issue with fresh profile without any extensions/apps or reset all the flags and let us know if issue still persists. Thanks.!
,
Aug 27
Yeah, I wouldn't expect you to be able to reproduce it. It's something that has happened to me randomly, with no known way to trigger it at will. Did you even read my report??
,
Aug 27
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 27
,
Aug 28
Now the colors have changed again. Are there any logs that I can inspect and attach??
,
Aug 28
If I go to chrome://flags and set "force color profile" to "sRGB", it fixes the issue. So, apparently, Chrome fails to detect "the color of the window's current monitor, as specified by the operating system" correctly. (and don't tell me it's the OS that reports the wrong profile, because Chrome is the only program affected). That there's NOTHING in Settings about this (no mention of color profiles at all) is absolutely pathetic. Flags are cool, but being able to check and control color profiles is something a user should be able to do in Settings, at least Advanced Settings. And not just force a specific color profile or choose to use the default, but also chrome should tell me what default is being applied and where it got it from.
,
Aug 28
Unable to reproduce the issue on reported chrome version #68.0.3440.106 and latest chrome version #70.0.3534.4 using Ubuntu 17.10 by following the steps as per comment#0. Hence removing Needs-Bisect label as it is not getting reproduced from TE end and requesting Internals>Compositing team to look into the issue. Thanks.!
,
Aug 31
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by teo8...@gmail.com
, Aug 26