Firefox drop-down menu (from menu bar) wrongly size on scaled display
Categories
(Firefox :: Menus, defect)
Tracking
()
People
(Reporter: giuseppe.passino, Unassigned)
Details
(Keywords: multi-monitors)
Attachments
(1 file)
|
38.51 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:79.0) Gecko/20100101 Firefox/79.0
Steps to reproduce:
My windows 10 laptop setup is an external 1920x1080 at 100% zoom and the laptop screen set-up as secondary, at 2560x1440 scaled at 150%.
I ran Firefox (79.0 - 64-bit, extensions disabled) on the scaled display and clicked on the hamburger (main, top-right) icon.
Firefox (79.0 (64-bit)) works fine on the primary (unscaled) display, but on the scaled display all the drop-down menus (extension, but also hamburger from firefox) are too small, and the contents are either not entirely visible (typically for the extensions) or need a scrollbar (like the main firefox menu).
I tried to run firefox with extensions disabled but the problem persists.
Actual results:
The drop-down menu was too small (vertically) and there was a scroll-bar to scroll to the bottom of the menu. Only a few items at the time were visible.
Also, drop-down menu form extensions behaved even worse as there was no scroll-bar so they were useless.
Expected results:
The full drop-down menu should have been shown. Note that this happens when firefox is in the unscaled - primary monitor.
Comment 1•6 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
| Reporter | ||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 2•6 years ago
|
||
Is this a recent regression?
| Reporter | ||
Comment 3•6 years ago
|
||
Since I had this monitor configuration (mid July) the bug has been present.
| Reporter | ||
Comment 4•6 years ago
|
||
Looks similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1588330
Comment 5•6 years ago
|
||
Yeah, this looks the same as bug 1588330. I'm going to close this as a duplicate of that bug. Thank you for filing this and bringing bug 1588330 back to my attention.
Description
•