Closed Bug 1725012 Opened 6 months ago Closed 6 months ago

Reduce arrow panel menuitem padding/margin in compact mode

Categories

(Firefox :: Theme, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
93 Branch
Tracking Status
firefox93 --- fixed

People

(Reporter: evilpie, Assigned: evilpie)

References

Details

Attachments

(2 files)

The increased size of the bookmark menu is probably one of the most common complains about proton. I think we should use the unsupported compact mode to address this.

Assignee: nobody → evilpies
Status: NEW → ASSIGNED
Attached image Screenshot
Pushed by evilpies@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/8363b7c72148
Reduce arrow panel menuitem padding/margin in compact mode. r=desktop-theme-reviewers,dao
Status: ASSIGNED → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → 93 Branch

Could this reduced vertical spacing be extended to popup panels as well, such as the Bookmarks menu that drops from the Menu Bar, and context menus? That would involve modifying the values in popup.css (at least for Windows, not sure about other platforms):

[uidensity=compact] menupopup > menuitem,
[uidensity=compact] menupopup > menu {
    padding-block: 4px;
}

Why limit this option to compact mode? I'm fine with the default non-compact layout except for the fat spacing of bookmarks/right click menus. It introduces an unnecessary amount of scrolling and mousing around.

(In reply to jscher2000 from comment #5)

Could this reduced vertical spacing be extended to popup panels as well, such as the Bookmarks menu that drops from the Menu Bar, and context menus? That would involve modifying the values in popup.css (at least for Windows, not sure about other platforms):

[uidensity=compact] menupopup > menuitem,
[uidensity=compact] menupopup > menu {
    padding-block: 4px;
}

I am not sure what this really mean. (My Firefox frontend experience only really extends to poking at it with the inspector) Please open a new bug with me cc'ed, preferably with a screenshot that shows what you want to modify.

See Also: → 1725873

There are already plenty of bug reports with several comments see bug 1722368
all the feedback comments here:
https://mozilla.crowdicity.com/post/720482

You will find most people are particulary verbal about the bookmarks because it probably has the most menu list items and therefore irrates the most. But generic uniformity should be maintained for all menu items.
Basically, all drop down menus that were effected by the unnecessary increase in space between menu items.
Any drop down menu from the Menu Bar eg: bookmarks
Drop down menu in the menu app hamburger.
Right click drop down menus etc.

People who have the ability are currently being forced to create and use userChrome.css to work around the usability issues.
People are just irritated by the inconvenience of extra scrolling which is slowing down work throughput and with repeated use, the current design helps to increase RSI issues.

So many thanks for realising this is a serious issue and helping to fix it quickly.

The fix is extremely limited and has no effect in the Menu Bar Toolbar and other areas.
Many people do not use the Bookmark icon - one reason - it starts on a lower toolbar and therefore does not allow the same amount of view of menu items in drop down menu.

Many people use the 'Menu Bar' because that's how they learned where menu's resided.
I use it because it is more practical and a lot quicker than via the Menu app icon.
I also do not like icons - I like words because then I do not lose where I am.
Not everyone only works using icons for many reasons.

You cannot design Firefox for a Phone and expect it to work for a PC - it doesn't.
The hundreds of posts on various forums should be sufficient proof that it is not a good design idea on PC's and not appreciated.

Can the fix be applied to all areas effected?

This is not a place for discussion. Please do appreciate that this is a volunteer effort, thank you. If you have specific issues please open new bugs.

You need to log in before you can comment on or make changes to this bug.