Firefox menus and panels overlap Windows Taskbar
Categories
(Firefox :: Menus, defect)
Tracking
()
People
(Reporter: arni2033, Assigned: chimaifeanyi29, Mentored)
Details
Attachments
(3 files, 1 obsolete file)
Comment 3•10 years ago
|
||
Updated•3 years ago
|
Updated•3 months ago
|
Submitted patch: https://phabricator.services.mozilla.com/D289514
"Hi, the patch has been approved with r+ by gstoll. Could someone with commit access please trigger autoland? Thank you!
Comment 7•3 months ago
|
||
:japandi, we can potentially land this if it's even still an issue, but this is not something we marked as a good first bug.. It's touching a .cpp file which our team rarely if ever works with. We'll need to test to make sure that it's still an issue a decade later.
Hi Kelly, I tested the reproduction steps from the bug report on Windows 11 with the latest Firefox Nightly. The context menu no longer overlaps the Windows taskbar, it stops correctly above it. Screenshot attached. The bug appears to still be present in the code (the default value is still 1) but Windows 11 may be handling it differently. Happy to test further if needed.
Comment 9•3 months ago
|
||
A reviewer in the #win-reviewer group that approved your patch can queue your patch to land if they're happy to accept it.
Comment 10•3 months ago
|
||
Note that the change here afftects all popups/panels, not just context menus.
| Assignee | ||
Comment 11•3 months ago
|
||
Hi Neil, thank you for the feedback. I noticed that macOS (Cocoa), GTK, UIKit, and Headless all already return 0 for MenusCanOverlapOSBar and work fine with all popup types. Should I be concerned about the impact on non-context-menu popups on Windows specifically? Happy to adjust the patch if needed.
| Assignee | ||
Comment 12•1 month ago
|
||
can you take a look into my patch and potentially land it thank you.
| Assignee | ||
Comment 13•25 days ago
|
||
I need this bug to be reviewed please, I need to know the guidance so that I can move forward, please.
Comment 14•23 days ago
•
|
||
(In reply to japandi from comment #13)
I need this bug to be reviewed please, I need to know the guidance so that I can move forward, please.
Neil should review the patch.
(In reply to Neil Deakin from comment #10)
Note that the change here afftects all popups/panels, not just context menus.
Is that not what other apps do? I tried quickly with notepad yesterday, on win11 that doesn't overlap the taskbar even with the main menus.
My only reservation here is that there's a chance this is going to increase the number of situations (ie screen size / density combinations) in which the main hamburger menu scrolls, on smaller screens. Neil, can you provide feedback on the patch, consulting with UX as needed? Thank you.
Comment 16•22 days ago
|
||
No, that seems fine. I only comment because the summary of the bug only mentions context menus.
Updated•15 days ago
|
Comment 17•15 days ago
|
||
Comment 18•15 days ago
|
||
Comment 19•15 days ago
|
||
Backout for causing multiple failures at largemenu.html
push with failure
failure log
backout link
| Assignee | ||
Comment 20•15 days ago
|
||
redirecting to a more experienced engineer.
Comment 21•15 days ago
|
||
(In reply to japandi from comment #20)
redirecting to a more experienced engineer.
This is your patch - it got backed out because it broke tests. To get it to land, you'd need to figure out why the test broke and whether that means there should be changes to your patch or whether the test needs updating (or a bit of both). The previous comments have links to more details of what broke; try looking at those, maybe running the test locally with/without your patch and seeing what behaves differently, or adding logging and debugging on try. If you have specific questions, ask for help from the mentor for this bug.
Comment 22•15 days ago
|
||
The failing test has a manual reference to assume that Windows doesn't overlap the OS bar.
https://searchfox.org/firefox-main/source/toolkit/content/tests/chrome/window_largemenu.xhtml#446
The test may just work by removing that assumption, now that the behaviour has changed.
But you should try running the test locally to verify.
| Assignee | ||
Comment 23•14 days ago
|
||
Updated•14 days ago
|
Updated•14 days ago
|
Updated•14 days ago
|
| Assignee | ||
Comment 24•6 days ago
|
||
I made an update to the patch, please let me know if I am right or wrong.
Comment 25•4 days ago
|
||
Comment 26•4 days ago
|
||
| bugherder | ||
Updated•4 days ago
|
Description
•