(minor visual glitch) Close button highlighted when dragging titlebar from maximized mode.
Categories
(Core :: Widget: Win32, defect)
Tracking
()
People
(Reporter: johnsmith94328, Unassigned, NeedInfo)
References
(Regression)
Details
(Keywords: nightly-community, regression)
Attachments
(1 file)
2.30 MB,
video/mp4
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/118.0
Steps to reproduce:
Click and hold on titlebar, drag downwards
Actual results:
browser exits from maximized, as expected, but close button is highlighted on its own for no reason.
Expected results:
The close button should remain idle since it has not been interacted with. It doesn't highlight when dragging in unmaximized mode, only when transitioning from maximized to unmaximized.
![]() |
||
Comment 1•1 year ago
•
|
||
I can reproduce this issue on Nightly120.0a1 Windows10.
And I can also reproduce on Firefox69.0....
STR:
0. Enable Snap windows
from Windows settings.
- Open Firefox.
- Switch to normal window size mode.
- Drag the title bar to the top edge of the screen with the mouse. Do not release the mouse button yet.
- Remember the position of the close button.
- Release the mouse button to maximize the browser.
- Press the mouse button at the position memorized in step 4. Then drag downward.
NOTE:
If the position to be memorized in step 4 is another button (e.g. List All Tabs button), that button will be highlighted (mouse hover status) in step 6.
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=32552726554321d35a8c18224343fe73ece324c2&tochange=0930049c0ca984c909d11ba2853ef6d96e43e242
Comment 2•1 year ago
|
||
:mconley, since you are the author of the regressor, bug 1534389, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Reporter | ||
Updated•1 year ago
|
Comment 3•1 year ago
|
||
As noted in comment 1, this also happens on Windows 10.
Comment 4•1 year ago
|
||
Set release status flags based on info from the regressing bug 1534389
Updated•1 year ago
|
Updated•1 year ago
|
Description
•