Window controls (minimize, restore/maximize, close) often get stuck in a :hover state
Reported by
emmybayl...@gmail.com,
Aug 11 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2824.0 Safari/537.36 Steps to reproduce the problem: 1. Open a Chrome window (maximized, preferably, as it's easier to reproduce the issue this way) 2. Hover your mouse cursor over one of the three window control buttons 3. Move your mouse quickly into the top chrome or the content of the web page What is the expected behavior? The buttons should fade once the cursor has left the area. What went wrong? Instead, the buttons can get stuck looking as if your cursor is still positioned over them. From what I can tell, the issue seems to be when the cursor jumps from a position on the title bar to a position below, where it "disappears" from the title bar's view, making it impossible to discern whether it's actually over the button in question. Did this work before? No Chrome version: 54.0.2824.0 Channel: dev OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0 I really wasn't sure how to best describe the issue, so apologies if the title isn't clear. It should be noted that this issue has been occurring (for me) at least since Chrome 50, and it's not a problem I've ever had with any other browser. This issue could potentially be difficult to reproduce depending on your mouse polling rate. I'm not sure--I have a very average Logitech mouse.
,
Aug 12 2016
Interesting! This appears to repro all the way back to Chromium 2.0, the earliest build I tried. Chrome's code doesn't seem to do anything special for WM_NCMOUSELEAVE, but we probably need to in order to clear the highlight?
,
Aug 15 2016
https://codereview.chromium.org/2244263002 When the user movers the cursor over the minimize/maximize/close buttons, DWM paints them in a hover state. If the user subsequently moves the cursor out of the window, DWM was not repainting the icons with the unhovered state because Chrome ate the WM_NCMOUSELEAVE message. This change notifies DWM of the exit.
,
Aug 16 2016
Issue 637827 has been merged into this issue.
,
Aug 17 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7af2fc83ecab219d9d2902db766ab0d2ba4dabf1 commit 7af2fc83ecab219d9d2902db766ab0d2ba4dabf1 Author: elawrence <elawrence@chromium.org> Date: Wed Aug 17 15:59:37 2016 Ensure window border icons repaint when DWM is enabled When the user movers the cursor over the minimize/maximize/close buttons, DWM paints them in a hover state. If the user subsequently moves the cursor out of the window, DWM was not repainting the icons with the unhovered state because Chrome ate the WM_NCMOUSELEAVE message.This change notifies DWM of the exit. BUG= 637114 TEST=Unmaximize Chrome. Hover Red-X at top right. Fling mouse upward. R=sky@chromium.org Review-Url: https://codereview.chromium.org/2244263002 Cr-Commit-Position: refs/heads/master@{#412541} [modify] https://crrev.com/7af2fc83ecab219d9d2902db766ab0d2ba4dabf1/ui/views/win/hwnd_message_handler.cc
,
Aug 18 2016
commit 7af2fc83ecab219d9d2902db766ab0d2ba4dabf1 was: initially in 54.0.2832.0
,
Aug 19 2016
Tested the same on win7 chrome version 54.0.2832.2 - observed that the close button fades once the cursor has left the area as expected. Hence adding TE-Verified labels. |
||||
►
Sign in to add a comment |
||||
Comment 1 by elawrence@chromium.org
, Aug 12 2016