Issue metadata
Sign in to add a comment
|
DevTools UI buttons randomly flicker
Reported by
luzar.da...@gmail.com,
Sep 24 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. open devTools What is the expected behavior? What went wrong? - the meatballs button (and sometimes the isnpect-DOM-elem button) is usually a gray block - upon click, the contextmenu buttons flicker reproducible in stable, incognito, and canary Did this work before? Yes 60 Chrome version: 61.0.3163.100 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Sep 25 2017
luzar.david@ Thanks for the issue. Unable to reproduce this issue on Windows 7, Mac OS 10.12.6, Ubuntu 14.04 on the latest Canary 63.0.3222.0 and latest Stable 61.0.3163.100 with the below steps. 1. Launched Chrome and opened any webpage 2. Opened Devtools and hovered the mouse pointer on the context menu. 3. Could observe that the 3 dot button of the menu is clearly seen and on hovering the mouse on the context menu, no flickering is seen. Please find the attached screen-cast for reference. Request you to please retry the issue on a new chrome profile without any flags/extensions and update the thread if there are any issues. Thanks..
,
Sep 25 2017
Thank you for providing more feedback. Adding requester "susanjuniab@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 26 2017
luzar.david@ Thanks for the feedback. Unable to reproduce the issue on Windows 7 and Windows 10 using the latest Stable 61.0.3163.100 and Canary 63.0.3223.8 after fresh installation of Chrome as well. Requesting someone from 'Platform>DevTools' team to please look into this issue and help in further triaging. Thanks..
,
Sep 26 2017
Just in case you are not aware, the issue seems to be related to (and being worked on in) https://bugs.chromium.org/p/chromium/issues/detail?id=768207 and connected to GPU rasterization in some way. If that's the case, this issue can be put on hold for now.
,
Sep 27 2017
robertphillips@/bsalomon@ - Could anyone please confirm if the issue is similar to issue id: 768207 and 755871. Thanks...!!
,
Sep 28 2017
It seems plausible but others (that I am adding) may know for sure.
,
Oct 2 2017
,
Oct 2 2017
I don't really know for sure, either. I'd need more information: (1) Can you please attach the chrome://gpu page for any machine that repros this. (2) Additionally, please try testing by turning off gpu rasterization in chrome://flags and seeing if it repros. (3) Finally, can you run chrome with gpu rasterization enabled, but passing the command line flag --disable-d3d11 to Chrome? See https://www.chromium.org/for-testers/command-line-flags for information about adding command line flags if you're not familiar with doing that.
,
Oct 3 2017
enne@ unsure who you're referring to. For me, this issue is identical with crbug.com/768207 (1) see attachment (2) yes, that solves it (unable to repro) (3) yes, that solves it, too (unable to repro)
,
Oct 3 2017
Thank you for providing more feedback. Adding requester "enne@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
,
Oct 3 2017
Thanks for all the help. :) I'll dupe this into that issue. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Sep 25 2017