Bookmarks menu incorrectly sized on some secondary display topologies
Categories
(Core :: XUL, defect, P3)
Tracking
()
People
(Reporter: sdl, Unassigned)
References
Details
Attachments
(4 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
When Firefox is positioned on a secondary display the rendering of and interaction with bookmark menus in the bookmarks toolbar is severely impaired. This issue only occurs if the secondary display is positioned logically above the primary display in the display topology; it will not manifest if the secondary display is adjacent to or beneath the primary display. All testing performed on a Windows 10 x64 system, so I'm unclear if the same issue applies to Linux or macOS systems.
Behaviour on top-level menus
- On opening a bookmark menu everything looks normal and bookmarks can be opened: https://imgur.com/9D4qM9A
- On dragging a bookmark to reorder the menu, the menu is resized to the full height of the secondary display: https://imgur.com/xuEB4ot
- The drag operation does however work as expected, so while ugly, this appears to be cosmetic.
Behaviour on nested menus (more serious)
- On opening a nested bookmark menu everything looks normal and bookmarks can be opened: https://imgur.com/uVleXTn
- On dragging a bookmark to reorder the menu, the menu is repeatedly resized to the full height of the secondary display and reordering bookmarks becomes effectively impossible. It's hard to capture this behaviour entirely in a screenshot, as it looks similar to the first issue, but the menu keeps resizing itself making the drag operation impossible: https://imgur.com/vstRkFi
- Due to the above the only way to reorder nested menus is to perform the operation on the primary display (or secondary display not positioned above the primary) or to open the Library window (Ctrl+Shift+B).
Reporter | ||
Comment 1•5 years ago
|
||
Reporter | ||
Comment 2•5 years ago
|
||
Reporter | ||
Comment 3•5 years ago
|
||
Reporter | ||
Comment 4•5 years ago
|
||
Reporter | ||
Comment 5•5 years ago
|
||
I've added the images as attachments to this bug report but will leave the Imgur links active for now.
Reporter | ||
Comment 6•5 years ago
|
||
Argh, I just found this bug which looks to be the same and was opened a long time ago (but with little activity in recent years): https://bugzilla.mozilla.org/show_bug.cgi?id=783929
This new bug report perhaps has more detail, particularly the isolation of the issue to the specifics of the display topology, but will leave it up to the admins as to whether they should be merged or otherwise?
Comment 7•5 years ago
|
||
Hello, I managed to reproduce the issue on Firefox 71.0, Firefox Beta 72.0b1, and Nightly 73.0a1, and i've set the component.
Updated•5 years ago
|
Comment 8•5 years ago
|
||
It could be a widget bug.
Updated•5 years ago
|
Comment 9•4 years ago
|
||
The priority flag is not set for this bug.
:bgrins, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Updated•2 years ago
|
Comment 10•7 months ago
|
||
Setting priority is no longer part of current triage processes, clearing needinfo.
Description
•