Open Bug 1711350 Opened 4 months ago Updated 2 months ago

Proton app menu doesn't fit in small screen

Categories

(Firefox :: Menus, defect, P2)

defect

Tracking

()

People

(Reporter: Oriol, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression, Whiteboard: [proton-hamburger-menu] [priority:2a])

Attachments

(2 files)

Without Proton, my laptop screen has enough space to show the full menu. But with Proton, it doesn't fit, so I have to scroll every time that I want to close the browser, since the exit button is at the bottom.

Please reduce all the unnecessary padding that was added between menu items if the screen is not big enough. Otherwise it's very bad UX.

See Also: → 1694802
Whiteboard: [proton-hamburger-menu]
Severity: -- → S4
Severity: S4 → S3

(In reply to Alin Ilea from comment #1)

This could be a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1694802

May seem so, but that bug says that the issue has been fixed on Windows?
I took my screenshot on Windows, with latest nightly. Using either 1280x720 at 100%, 1600x900 at 125%, or 1920x1080 at 150%.
Same problem in Ubuntu with KDE plasma using 1280x720.

Priority: -- → P2
Whiteboard: [proton-hamburger-menu] → [proton-hamburger-menu] [priority:2a]

To be clear, this try build uses a simple patch to compact the space around the Zoom controls: https://treeherder.mozilla.org/jobs?repo=try&revision=1c1bfba6b85d556760a8d8b2475ecda5b1686f7e

Attached image try-build.png

With this try build I can at least click the exit button without scrolling, but it's only partially visible, so it looks very wrong.

Also, if there is an update or something that adds an extra item to the menu, the exit button will go completely out of view again.

Flags: needinfo?(oriol-bugzilla)

In that case, needinfo'ing back to rtestard for guidance on how Product would like to proceed.

Flags: needinfo?(rtestard)

Ping rtestard.

Also, even build from comment 4 still looks bad, at least is an improvement. Better that than nothing.

Apologies for the long delay here!
I agree that this is an improvement - this seems OK to ship if there is low risk of introducing new regressions (we had such issues before on the app menu although this feels potentially different if focus is on the specific Zoom area).
Overall bug 1698896 seems like the way to understand the share of users impacted by the scroll-bar (and if we should decide on trade-offs to make scrollbars appear less in this area).

Flags: needinfo?(rtestard)
You need to log in before you can comment on or make changes to this bug.