1707717 - Bookmarks panel goes beyond screen when fully expanded

Status: NEW

(Firefox :: Bookmarks & History, defect, P3)

Description

[Peter deHaan [:pdehaan]]

This comment is copy/pasted from a community issue filed during the Foxfooding program.

---

Firefox Version: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:89.0) Gecko/20100101 Firefox/89.0
Window Size (inner width and height): 1536x711

Steps to Reproduce

1. Click on Bookmark this Page
2. Expand Show All Bookmarks folder
3. Expand Tags

Expected Behavior

Fit to screen

Actual Behavior

The Save and Remove bookmark buttons go beyond screen.

Comment 2

[Bernard Igiri]

Could you please add a screenshot of this issue?

Comment 3

[Peter deHaan [:pdehaan]]

Attachment: scrollbars on macOS (15" rMBP)

In some cases I can see scrollbars on macOS when expanding both the Bookmarks and Tags sections. Other times, if the window if full width/height [not maximized, just full available screen size], the pop up panel will not show any scrollbars. So I think this is only showing scrollbars on small resolution screens or when things won't absolutely fit.

Comment 4

[Peter deHaan [:pdehaan]]

Attachment: full_width_height_macOS.png

Screenshot showing the window at full width/height on my macOS laptop and no scrollbars when opening both sections in the Edit bookmark panel.

Comment 5

[Bernard Igiri]

This is still unclear. I think we need UX feedback as there are many potential solutions for this, from shrinking the height of certain elements, to rearranging the layout on smaller resolutions, to keeping the Remove and Save buttons outside of the scrolling div. Blake Winton suggested putting this in the “Blocked Issues” sprint. I'm not sure how to do that unfortunately.

Comment 6

[Bernard Igiri]

This is now in the "Blocked Issues" sprint.

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:mak, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 8

[Marco Bonardo [:mak]]

The solution here is in bug 1464580.