minimize/maximize/close button's tooltips are mispositioned after resizing the window
Categories
(Core :: XUL, defect)
Tracking
()
People
(Reporter: 6k64x4ma, Assigned: emilio)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/109.0
Steps to reproduce:
- Unmaximize the Firefox window.
- Hover over the minimize/maximize/close button until the tooltip appears.
- Make the window wider.
- Hover over the tabstrip where the minimize/maximize/close button used to be.
Actual results:
The tooltip will pop up from wrong position.
Expected results:
The tooltip shouldn't be shown.
mozregression pointed to Bug 1801956 as a regressor,
but the tooltip is not displayed at all from Bug 1790616 until Bug 1801956.
Comment 1•1 year ago
|
||
:emilio, since you are the author of the regressor, bug 1801956, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 2•1 year ago
|
||
The issue here is that DealWithWindowsAppearanceHacks doesn't run unless
we're actually painting a background because we look at
mDefaultAppearance
and nsIFrame only checks HasAppearance
.
However this code can be simplified a bit, now that we cleaned up
background propagation in bug 1665476.
Enter in AppendBackgroundItemsToTop unconditionally, and clean up a bit
while at it.
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Set release status flags based on info from the regressing bug 1801956
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 4•1 year ago
|
||
Set release status flags based on info from the regressing bug 1801956
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5d628737431d Simplify background painting. r=tnikkel,layout-reviewers
Comment 6•1 year ago
|
||
bugherder |
Comment 7•1 year ago
|
||
The patch landed in nightly and beta is affected.
:emilio, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox110
towontfix
.
For more information, please visit auto_nag documentation.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 9•1 year ago
|
||
Reproducible on a 2023-01-20 Nightly build on Windows 10.
Verified as fixed on Firefox 111.0b5(build ID: 20230223185944) and Nightly 112.0a1(build ID: 20230223172038) on Windows 10 and Windows 11.
Description
•