Pages with solid background colour have "tiled" background
Reported by
anowlcal...@gmail.com,
Feb 16 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36 Example URL: http://mragheb.com/NPRE%20402%20ME%20405%20Nuclear%20Power%20Engineering/ Steps to reproduce the problem: 1. Set a solid background-color with one or two RGB components significantly less than the other(s) 2. Fill some, but not all, of the page with content 3. Observe "tiling" effect, where portions of the page that do not have content have the wrong background colour. What is the expected behavior? The background should be a solid colour – in the first screenshot, it should all be #00ffff. What went wrong? Where there's content, the background is the correct colour (#00ffff). However, in tiles with no content, the background is #82ffff instead (see attached screenshot). 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? Yes Chrome version: 64.0.3282.167 Channel: stable OS Version: Ubuntu 16.04 Flash Version: 28.0.0.161 This is exclusive to Chromium, as far as I can tell – Firefox displays the background correctly. In addition, I can't reproduce it on my Chromebook (nyan_big), so it may be GPU-specific (I've attached the contents of chrome://gpu on the device the issue appears on). The problem isn't limited to this particular website, it also happens on e.g. Trello. I've also attached a simple HTML file that demonstrates the behaviour -- the background-color is set to #008888.
,
Feb 18 2018
,
Feb 19 2018
Thanks for filing the issue! Checked the issue on reported chrome version 64.0.3282.167 and on the latest Dev 66.0.3350.0 using Ubuntu 14.04 with the below mentioned steps. 1. Launched Chrome version 64.0.3282.167 2. Navigated to http://mragheb.com/NPRE%20402%20ME%20405%20Nuclear%20Power%20Engineering/ 3. Downloaded and opened the file "colour.html " We are able to see the background colour properly with out any issues, attaching the screen cast of the same. Note: We are able see similar behaviour in chrome and other browsers too. @Reporter: Could you please check the screen cast and let us know if we have missed anything while reproducing the issue. Any further inputs from your end helps us to triage the issue in a better way.
,
Feb 19 2018
You haven't missed anything, that's exactly what I did. Presumably it's something strange about my GPU that's causing it...
,
Feb 19 2018
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
,
Feb 20 2018
It sounds like a GPU bug and I see you're running with Mesa driver. What happens if you try running with the added flag, either --disable-gpu (which will turn off GPU compositing) or --use-gl=swiftshader (which will use a software GL implementation).
,
Feb 20 2018
,
Feb 21 2018
I have had problems with graphics on this machine in the past, so a GPU bug would not be surprising. --disable-gpu fixes it, but --use-gl=swiftshader does not.
,
Feb 21 2018
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
,
Feb 21 2018
As per comment#8 by reporter it seems the issue is not seen when the flag --disable-gpu is enabled. Requesting kylechar@ for further help as enabling flag --use-gl=swiftshader doesn't help. @Reporter: Could you please let us know if we can close the issue as this seems to be resolved when one of the above two mentioned flags is enabled. Thank you!
,
Feb 21 2018
If it's not a Chrome bug, I guess there's no point keeping it open :) --disable-gpu (or disabling "Use hardware acceleration" in chrome://settings) also clears up some other graphical issues I've been having (e.g. flickering when translucent elements are present), so I guess I'll keep doing that.
,
Feb 21 2018
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
,
Feb 23 2018
As per comment #6 and #11, it seems to be a gpu bug and not a chrome specific. Hence, marking it as wontFix. Thanks...!! |
||||||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||||||
Comment 1 by bokan@chromium.org
, Feb 16 2018