would love to have less Menu Entries

[dhouwn]

I would love to have less menu entries but at the same time I want to allow/disallow sites on full-domain and full-address basis (latter until mixed-content protection gets improved) and sometimes do that temporarily too, therefore I would love to see ideas on that being implemented (might also help the general user a lot in environments where vertical screenspace is valuable).

One such idea I outlined in my head was to somehow fold temporarily and permanently allowing menu an entity into one, e.g. you would first choose a domain and then whether you want to allow it permanently or temporarily, or alternatively (in order to save clicks) that whether you allow something one way or another depends on a modifier (e.g. a key being pressed).

I am just brainstorming here and my concepts are on purpose just sketchy, feel free to join me and Giorgio please tell whether in general you would be in favor of such UI compacting measures.

[Thrawn]

How about putting 'Allowed sites' (with options to deny) and 'Blocked sites' (with options to allow) on submenus? That way, they never share vertical real estate with each other or with the other menu options. It would mean extra navigation to reach the sites you want to allow, though.

Alternatively, just 'Allowed sites' could move to a submenu, leaving blocked sites on the main menu? So it's just as fast to get to sites that you need to unblock, but space usage is reduced for the options to re-block sites (which you don't do as often).

[GµårÐïåñ]

Group by domain only and decisions made under submenu instead sounds like something I would/might like for the sake of tidiness but that "extra" maneuvers might save vertical space but might be considered convoluted and unnecessarily labored. Not sure. Think about it, if you have ever used RP, you know you have menu, submenu, submenu, submenu sometimes that seem endless and I am ok with it and gotten used to it but I know many who find that unnecessary and wish it was more NS like believe it or not, meaning all options in front of you. If it wasn't such a hassle to do, maybe Giorgio could give an option that would present the menu both ways for those who like it in each way but that is an unfair amount of work to ask someone to do.

[Thrawn]

Yeah, it's important to reduce the number of actions needed to whitelist sites (and get the current page working), hence the keyboard shortcut to allow top-level site, 'Allow all this site', etc. Leaving the blocked sites on the top-level menu makes sense.

I still like the idea of moving the allowed sites to a submenu, though, because you don't normally need to interact with them again. Temporarily allowed ones are a slightly different story, but still, you can make all temporary permissions permanent, or revoke them all, from the main menu, so having the individual sites on a submenu doesn't seem too onerous.