Hover comes back immediately after dismissing app menu with a click |
||||||
Issue descriptionVersion: 52.0.2716.0 OS: Windows What steps will reproduce the problem? (1) Click app menu icon to bring up the app menu (2) Click the icon again to dismiss the menu What is the expected output? In ripple is deactivated (explodes). Hover comes back after a delay. What do you see instead? The ripple is hidden quickly and the hover effect appears almost immediately. Please use labels and text to provide additional information. Seems to work better on Linux / Chrome OS.
,
May 4 2016
,
May 4 2016
I suspect you are getting an immediate hover showing up on mouse release due to the button receiving mouse enter/exit events. It is very unfortunate that the event streams being dispatched to the View's are different on each platform. Is it reasonable/feasible to tackle making the events streams the same across the platforms? Who would know?
,
May 4 2016
It would be good to confirm we actually get different events on these different platforms -- that would surprise me a bit. +CC sky/msw to comment on this issue; maybe they know if there aare differences here.
,
May 4 2016
Sorry, I'm not sure why Windows and Linux would differ here. Hopefully it's easy to get a backtrace on the button state change to hover. Windows' behavior feels correct (at least pre-MD), showing hover instantly after the menu closes, since the mouse is indeed hovering over the button. Linux seems odd in that the hover state only returns after some mouse movement. Perhaps Linux should also return to hover immediately, but the MD animation code should complete the close animation and then transition to the hover state. Sorry I don't have more offhand knowledge here.
,
Jul 12 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 12 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 12 2017
Windows is now delayed. I kinda agree with comment 5 that this seems vaguely odd to me, but at least the inconsistency reported here looks gone. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by pkasting@chromium.org
, May 4 2016