If you resize small pop-up windows, hamburger menu icon can be made to overlap URLbar and not-be-clickable
Categories
(Firefox :: Theme, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox112 | --- | wontfix |
| firefox113 | --- | wontfix |
| firefox114 | --- | verified |
People
(Reporter: dholbert, Assigned: emilio)
References
(Regression)
Details
(Keywords: regression)
Attachments
(7 files)
STR:
- Visit https://www.sfcu.org/membership-rewards/
- Click "Live Chat" link at top left (note that your browser has to be at least ~1000px wide for it to show up)
- Resize the pop-up window that appears to be skinnier -- as skinny as you can make it.
ACTUAL RESULTS:
The hamburger button gets pushed "behind" the location bar, BUT its hamburger icon remains visible! It's still not clickable, though, even though it sorta looks like it would be. Any clicks are instead sent to the location-bar UI that it's overlapping.
[edited to remove the part about the extension-menu-button getting partially and then fully pushed behind the location bar -- that behavior has evolved a bit, per comment 2]
EXPECTED RESULTS:
- Buttons should not be pushed underneath other UI. They should be pushed off the edge of the UI and clipped, instead. (That's what used to happen before this regressed, at least.)
- Hamburger icon menu shouldn't be visible-and-yet-unclickable.
Regression range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a4a8521b307275498ecda987249e72150c3c110d&tochange=0645b630915e38a3a37d076aa7f431a72387699e
In that range, bug 1795260 looks like it would've been what regressed this.
| Reporter | ||
Comment 1•3 years ago
|
||
| Reporter | ||
Comment 2•3 years ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #0)
ACTUAL RESULTS:
(A) As it shrinks, the extension-menu-button gets partially and then fully pushed behind the location bar.
Actually -- in current Nightly (2023-04-07), the extension menu button stays in place (hooray!) but the hamburger menu overlaps it even with the initial size of the window (darn) and still gets pushed underneath/beyond it.
| Reporter | ||
Comment 3•3 years ago
|
||
Comment 4•3 years ago
|
||
:emilio, since you are the author of the regressor, bug 1795260, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Comment 5•3 years ago
•
|
||
(In reply to Daniel Holbert [:dholbert] from comment #2)
Actually -- in current Nightly (2023-04-07), the extension menu button stays in place (hooray!)
[answering my own curiosity: mozregression says that this improvement came from Bug 1820743 ]
but the hamburger menu overlaps it even with the initial size of the window (darn) and still gets pushed underneath/beyond it.
I spun off bug 1827031 on this observation.
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 6•3 years ago
|
||
I'm not convinced this is the right fix but we're fundamentally out of
space otherwise...
Updated•3 years ago
|
Comment 7•3 years ago
|
||
Set release status flags based on info from the regressing bug 1795260
Updated•3 years ago
|
Comment 9•3 years ago
|
||
| bugherder | ||
Comment 10•3 years 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-firefox113towontfix.
For more information, please visit auto_nag documentation.
| Assignee | ||
Updated•3 years ago
|
Comment 11•3 years ago
|
||
Comment 12•3 years ago
|
||
The issue doesn't happen for 112 on the release channel.
| Reporter | ||
Comment 13•3 years ago
|
||
(In reply to Suhaib Mujahid [:suhaib] from comment #12)
The issue doesn't happen for 112 on the release channel.
Yes it does, for me at least. (I tested 112 as well as 111 release and both were affected. I imagine release versions are affected as far back as 108 given the regressor bug 1795260.)
Note that this bug is specific to popup windows (e.g. the one launched from the "live chat" link on https://www.sfcu.org/membership-rewards/ ), and your screenshot doesn't seem to show a popup window -- the firefox window shown there has a bookmarks toolbar, and back/forward/reload icons, which indicate that it's a regular window rather than a popup.
But in any case: wontfix for 112 seems reasonable.
| Reporter | ||
Comment 14•3 years ago
|
||
Here's a screenshot in current Nightly, where I've shrunk the popup to be as skinny as possible. There's no space to show much of the URL, of course, which is to-be-expected given the shrinkage. But the buttons are all visible, non-overlapping, and functional. Hooray!
| Reporter | ||
Comment 15•3 years ago
•
|
||
Marking as verified-fixed for v114 Nightly, per comment 14.
Comment 16•3 years ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #13)
Yes it does, for me at least. (I tested 112 as well as 111 release and both were affected. I imagine release versions are affected as far back as 108 given the regressor bug 1795260.)
Sorry, you are right. I can repreduce it on 112 release with a popup window. But not the regular window.
Note that this bug is specific to popup windows (e.g. the one launched from the "live chat" link on https://www.sfcu.org/membership-rewards/ ), and your screenshot doesn't seem to show a popup window -- the firefox window shown there has a bookmarks toolbar, and back/forward/reload icons, which indicate that it's a regular window rather than a popup.
I was able to reproduce this on 113, even on the regular window.
Comment 17•3 years ago
|
||
Here is a screenshot where the issues happen on 113 regular window.
| Reporter | ||
Comment 18•3 years ago
•
|
||
Thanks for clarifying. I can reproduce that issue as well, and I can confirm that issue is fixed in current Nightly. I used mozregression --find-fix to find when that was fixed, and it seems it was bug 1827031 that fixed that regular-window-problem, rather than the patch for this bug here.
So: the hamburger/extension overlap in comment 17 is a version of bug 1827031, not this bug here.
Description
•