Issue metadata
Sign in to add a comment
|
Flickering elements with border-radius
Reported by
ja...@realfoto.ca,
Sep 27 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Example URL: http://www.cssdesk.com/DmNfg Steps to reproduce the problem: 1. Click around on the page. Click on button etc. 2. Scroll in the side bar 3. See flickering on the blue button. What is the expected behavior? Stable display of buttons What went wrong? Flickering of colour on elements that seems to be tied to border-radius or maybe border-radius and other styles. No consistent behaviour. As you move the cursor around the screen or scroll different divs with similar styling will have parts of them flicker. Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? Yes Does this work in other browsers? Yes Chrome version: 61.0.3163.100 Channel: stable OS Version: OS X 10.13.0 Flash Version: Seems to have changed when I upgraded to High Sierra. Other computers still on Sierra do not have the same issue.
,
Sep 27 2017
I'm seeing different UI for the above URL (http://www.cssdesk.com/DmNfg) when compared to the attached screenshots. Can you please double check? Thank you!
,
Sep 28 2017
Sorry, the screenshots of a private web app for my company so I cant link to that directly, so I took some screenshots of it and made a cssdesk that reproduces the effect. Here is a screenshot of it in cssdesk.
,
Sep 28 2017
Thank you for providing more feedback. Adding requester "manoranjanr@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
,
Sep 29 2017
The comment about the behavior changing when switched to High Sierra is interesting, as it suggests a bug in graphics drivers or some other OS issue. It looks like portions of the background image are disappearing, but not all. Is that right? How confident are you of the High Sierra connection? Do you know whether Chrome also switched versions at the same time? Can you confirm that the Chrome version is identical on the machines that are not experiencing the bug? This may be a little tricky for us to work on. We are not allowed to update to High Sierra on our work machines. Sorry.
,
Sep 29 2017
My Chrome versions were not identical. But I have updated the other computer so that they now are, but non-high sierra (its running Sierra) is still not flickering. I understand that this is a very etherial problem. It was just the first time I had an issue and a google search didn't seem to have anyone else reporting it. It's not the end of the world, just annoying ;)
,
Sep 29 2017
Thank you for providing more feedback. Adding requester "schenney@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
,
Sep 29 2017
> This may be a little tricky for us to work on. We are not allowed to update to High Sierra on our work machines. Sorry. schenney@ - try contacting spqchan@ who has an off-corp 10.13 Mac you might be able to borrow.
,
Oct 2 2017
Thanks shrike@. I'm passing the bug off to the GPU team as this is almost certainly an issue with the new MacOS, which means not something in Blink layers of the code.
,
Oct 4 2017
I'm also experiencing similar UI glitches with the same version of Chrome and Mac OS as the reporter. I believe they are the same problem. I don't know the specific cause or types of UI elements affected, but it affects Google Drive, Asana and Gmail. Chrome version: 61.0.3163.100 Channel: stable OS Version: OS X 10.13.0 Definitely happened immediately after switching to Mac OS 10.13, and I can confirm that Chrome was not updated during that time.
,
Oct 16 2017
The NextAction date has arrived: 2017-10-16
,
Oct 16 2017
Could anyone seeing issue like this please provide us with the "About this Mac' data on hardware version? We're seeing various problems with 10.13 and certain hardware and we're trying to figure out exactly what hardware is responsible. Some changes recently landed in Chrome that might fix this. Could folks please try Chrome Canary and see if the problem was related to one of those fixed issues?
,
Oct 30 2017
The NextAction date has arrived: 2017-10-30
,
Oct 30 2017
Closing due to lack of feedback. Reopen if feedback is available for comment #c12. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Sep 27 2017