Colors of websites rendered incorrectly after resuming laptop from suspend
Reported by
alexande...@gmail.com,
May 22 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.170 Safari/537.36 OPR/53.0.2907.57 Example URL: php.net Steps to reproduce the problem: 1. Visit php.net on laptop while not being docked 2. Suspend 3. Connect laptop to docking station and resume What is the expected behavior? The colors appearing as they should. What went wrong? Colors on website appears to be off by a few nuances. Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? N/A Does this work in other browsers? No Opera 53 Chrome version: 66.0.3359.170 Channel: stable OS Version: Ubuntu 18.04 Flash Version: Shockwave Flash 29.0 r0 See https://askubuntu.com/questions/990533/color-change-in-chrome-and-opera-after-resuming-from-suspend
,
May 22 2018
,
May 22 2018
Might be related to x11 support for multiple monitors? https://chromium-review.googlesource.com/972547 https://chromium-review.googlesource.com/1020150 In general we could be much more aggressive about re-checking the color space for a window on Linux.
,
May 23 2018
Could possibly be ICC profiles, yes. The colors seem to follow the settings for the screen that was connected/in use whenever the application (Chrome/Opera) was opened. If I suspend and resume and only use my laptop screen, the colors are off again. If I leave the browser open, suspend and resume while docked, they are okay.
,
May 23 2018
As per comment #0 we don't have docking station to test this issue.Hence adding TE-Hardware-Dependency label to this issue. Thanks.!
,
May 23 2018
Maybe just using an external monitor on the laptop would do? And only show output on that. Then open a browser window, suspend the machine and disconnect the monitor and finally, resume.
,
Aug 17
Assigning to hubbe for triage/investigation.
,
Oct 22
It looks like X11 doesn't provide a way to notify us if the monitors have changed, which would mean that we would need to poll the xrandr data in order to find that out. I'm not sure we actually want to do that. Marking as WontFix for now, feel free to re-open if anybody can think of a reasonable way for how this ought to work. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by chrishtr@chromium.org
, May 22 2018Components: -Blink Internals>Compositing>Rasterization