Messages

The expanded view ofcourse :)

Ah, if you mean simply the expanded view in the sidebar, that should be doable. I will look into it.

I don't see how that could be sensibly changed. Only leaf menu items (Users in this case) actually have a page associated with them, the parent menu items are just group headings. So there is nothing opening them in a new tab is actually able to show, hence the behaviour.

I can't say for 100% sure, but I am pretty sure that it can be done, however I am not a webdeveloper so I could be horribly wrong! :)

Yes, anything in theory can be done, but it still comes back to the question - what would the new tab show?

Example :

- System
-- Access
--- Users

Only Users can be opened in a New Tab ;)

Mouse/Touchpad Middle Click or CTRL+Click = Open link in New Tab.

Got it. I don't see how that could be sensibly changed. Only leaf menu items (Users in this case) actually have a page associated with them, the parent menu items are just group headings. So there is nothing opening them in a new tab is actually able to show, hence the behaviour.

In my opinion, the biggest problem with the menu is that you can "middle click" to nothing. If you have not reached the last level of the menu with the actual settings...

Not sure I understand what you mean by this?

Disabling automatic menu collapsing in my mind would quickly lead to a monstrosity.

I agree - I would never use the toggle xD

As a separate proposal, I was also contemplating adding a toggle setting that could disable automatic menu collapsing generally. I think the scroll would probably still need to happen though.

https://github.com/opnsense/core/pull/10033

Yes, as I said. It was not me who enabled it though. This only occurred when I had to abort the opnsense-revert script. Somehow that caused the OPNsense repo to be disabled and the FreeBSD repo to be enabled

The further alternative, which is probably the cleanest (but a little more challenging to implement).

See attached

IMHO similar to Enabling/Disabling KEA/DNSmasqd on Multiple Interfaces but maybe with some improvements :)

I don't think you can equate the two. There are just a few interfaces that appear in the list in your example. There are on the other hand dozens of leaf pages. Also a dropdown in a menu item would look super odd imo - not even sure it is possible.

Anyway, I'm preparing an alternative that has a small star in each breadcrumb heading. Unobstrusive and not "Super Mario World" to my eye

I realised when doing this everyone would have an opinion xD

I thought about the first option. It seemed cumbersome to me. To add a Favorite, you would need to click a button and then navigate a list and click another?

I also thought about the second option. The issue with that is there isn't consistency between pages that would make adding an icon or setting there convenient or consistent. Probably the only realistic spot to add it is at the start or end of the heading on the page.

The nice part though of having the favorite icon in the menu is that multiple options can be clicked without having to open each page.

Maybe Franco or Ad will see this and can weigh in from a preferred UI perspective before I finalise a PR.

I'm proposing to submit a PR shortly to implement a Favorites section.

• It only appears if the user has at least one favorite selected. If all favorites are removed, the Favorites section disappears
• Favorites are added/removed simply by clicking on a star icon next to each leaf menu item. The star icon changes appearance if the item is in the Favorites list
• The Favorites list is stored per-user, and is subject to their permissions
• If a favorited menu item is removed (eg an interface is removed or a plugin uninstalled), the Favorites entry is also removed
• Favorites entries appear in the same order as the corresponding menu items

Some sample screenshots attached.

FWIW, it seems that the original "hung" state of opnsense-revert was caused by a file lock on config.xml by configd, which prevented run_migrations.php from acquiring it

I've managed to deal with that - that wasn't fun.

It appears that when I had to abort opnsense-revert because it hung, the FreeBSD repo was somehow enabled. Then when I ran opnsense-revert again, pkg was updated to the FreeBSD version (2.5.1), which obviously led to some conflicts.

I had to go through a process of disabling the repo, deleting the pkg database, and force reinstalling OPNsense. Then checking there weren't any rogue packages on the system from the FreeBSD repo.

Ugh.