947301 - Add ability to remove Hamburger Menu button

Status: RESOLVED WONTFIX

(Firefox :: Toolbars and Customization, defect)

Description

[Alice0775 White]

Please add ability to remove Hunbergar Menu button from nav Bar if Menubar is enabled  at least

Comment 1

[Alice0775 White]

Sorry,
s/Hunbergar/Hamburger/

Comment 2

[Jared Wein [:jaws] (please needinfo? me)]

A major part of Australis is to reduce the ability for people to make errors that cause the browser to "not work" for them later on down the road. It is possible that the user could enable the menubar, hide the Hamburger button, then hide the menubar, leaving no visible way for users to "fix" their browser.

Keeping the Hamburger button visible in all states will also help SUMO with directing users around their browser. The menubar is in a different location per platform, so that is much harder to give directions to users.

Comment 3

[Alice0775 White]

this is not reasonable for me.

If user hide the menubar, then the Hamburger button is AUTOMATICALLY visible.
That's it. right?

Comment 4

[Alice0775 White]

(In reply to Jared Wein [:jaws] from comment #2)

> Keeping the Hamburger button visible in all states will also help SUMO with
> directing users around their browser. The menubar is in a different location
> per platform, so that is much harder to give directions to users.

To give directions to users, just mention "Help – Restart with Add-ons Disabled…"

Comment 5

[Dave Garrett]

There shouldn't be anything preventing an addon from doing this sort of thing. If a user wishes to remove this button and use only the traditional menu bar then doing so via an addon would be simpler and more reliably fixable. Reverting would be just a matter of uninstalling/disabling an addon that would be clearly listed in the Addons Manager rather than having to search through the customization system. It would also automatically revert in safe mode or on Firefox reset.

Note that just because I am of the opinion that this would be better served in an addon (possibly also with other simple but problematic UI changes as options) doesn't mean I don't think the UX team shouldn't write it. People have a point that Firefox gets used for its customizablility. The best way to maintain this is to have Firefox developers write addons for customization when they move a feature from in-product customization to addon-based customization.

Comment 6

[Dave Garrett]

I was actually considering writing a little Australis customization addon myself, but screw that, this guy made an awesome one already:
https://addons.mozilla.org/firefox/addon/classicthemerestorer/

It allows for all manner of customization, including removing the new menu button, adding back the old menu button, or even ditching both and going back to just the classic menu bar. I say this guy should just get bumped up in the AMO editor review cue and Mozilla should link directly to it when people want to know how to customize these things now. ;)

Comment 7

[Marc Auslander]

What I really want is to be able to move the hamburger to the left, where IMHO it belongs.

Comment 8

[Sebastian Zartner [:sebo]]

> It is possible that the user could enable the menubar, hide the Hamburger button,
> then hide the menubar, leaving no visible way for users to "fix" their browser.
I agree with Marc on this. If it's intended to not allow people to hide the menu button, then you should at least allow them to move it within the main toolbar.

Sebastian

Comment 9

[Zack Weinberg (:zwol)]

Consider, please, that on OSX the menu bar is baked into the system and can't be turned off; the hamburger is completely redundant and is wasting my VALUABLE HORIZONTAL SCREEN SPACE.  ... Just kidding about that last part; 16:9 aspect ratio means if anything I have too *much* horizontal and not nearly enough vertical.  But the point remains: the hamburger is redundant on OSX, and although I *can* see an argument for keeping it around for consistency with our other OSes, I do think I should be able to get rid of it if I want, and without having to install extensions.  I actually came here because I was surprised to discover that the hamburger can't be *moved*, which is surprising and inconsistent with how everything else can be.

Regarding "what if the user turns off both the hamburger and the main menu," (on menubar-inside-window systems), detect that situation and turn the hamburger back on.

Comment 12

[j. 'mach' wust]

You can easily hide the menu button (redundant on Mac OS X) without a dedicated add-on by means of userChrome.css, as smsmith has pointed out on mozillaZine (and probably others otherwhere): http://forums.mozillazine.org/viewtopic.php?p=13496723#p13496723

#PanelUI-button {
    visibility: collapse !important;
}

Comment 14

[Dinar]

duplicates: bug 943038, bug 958366, bug 1007586

Comment 15

[Dinar]

related to bug 940418, it is requesting not removing, but moving menu button.

Comment 16

[:Gijs (he/him)]

Realistically, I don't see this getting fixed; I don't even think we'd take a patch to do what's proposed in comment #3 and have some kind of magical behaviour where either the menubar or the hamburger menu are forced to be visible. It's a bunch of work to implement, add automated tests, keep everything working in new configurations we're exploring (VR, IWA/PWA, etc.) so it's high cost, there are a bunch of open questions (how would we communicate this restriction to users in a useful way? what happens to panels we open automatically (ie without user interaction) anchored on the hamburger menu, like update and add-on install messages? What happens in popups - do we show the menubar even when it's turned off by the webpage if the user has the hamburger menu turned off?) so it adds uncertainty, and it would ultimately benefit a tiny number of people who currently have something of a workaround (userChrome.css) anyway.