Malfunctioning top chrome buttons: profile button is non-functional, other buttons have no hover effects |
||
Issue descriptionVersion: 49.0.2623.87 OS: Windows 10 In all windows in all profiles, the top chrome is not responding to mouse events correctly. 1. The profile button correctly turns blue on hover, but left- and right-clicking have no effect whatsoever. I cannot access the profile menu at all. What is the expected output? What do you see instead? 2. Hovering over buttons in the top chrome doesn't change their view to the on-hover state; they remain normal. This includes bookmarks, navigation buttons, extension icons, and the 3-dot chrome menu button. 3. The bookmark star in the omnibox doesn't change on hover, but does turn filled-in once clicked. However, it cannot be clicked again to un-bookmark (stays filled in), and no menu or dialog is shown when clicking or right-clicking. Other things respond normally to hover events, including: tab titles and their (x) close buttons; the omnibox, including badge and dropdown options. Flags include --enable-extension-action-redesign and --top-chrome-md=material -- not sure what their defaults are today.
,
Mar 11 2016
Do you get different results if you turn off material design?
,
Mar 12 2016
Well, restarting Chrome fixed everything. So toggling the flag doesn't break or unbreak it now. This has happened to me on earlier versions, at least for the profile button, so it'd be nice to figure out why. I'll see if I can find anything correlated to when it happens.
,
Mar 23 2016
If you are using material design on the latest dev or canary channels you should be seeing hover effects and the profile button should be functional. Please re-open if that is not the case and include the Chrome version you're running.
,
Mar 28 2016
Well... it wasn't functional, on 49.0.2623.87, two weeks ago. What makes you think that bug has disappeared? Please provide more information when marking regressions as WontFix so I know how to route further issues. |
||
►
Sign in to add a comment |
||
Comment 1 by michae...@chromium.org
, Mar 11 2016