starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

v3.0 beta - menu enhancement request #5094

New Issue
Closed
opened 2025-12-29 19:24:11 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:24:11 +01:00
Owner
Copy Link

Originally created by @tomaskir on GitHub (Jul 23, 2021).

NetBox version

3.0

Feature type

New functionality

Proposed functionality

Menu should not close each time you change a view. It makes navigation a bit tedious. For example, when in the Racks view (and its subviews), keep the Organization section of the menu should stay extended.

Use case

Menu in 2.11 has no animations (faster navigation) and the menus groups being horizontally side-by-side makes visually identifying where things are faster - building "visual memory" for where to click to get to a particular view is quite easy due to the static positioning and each element having unique position is easier.

In 3.0, due to animations and everything being in the same vertical menu (with dynamic position due to scroll), it means you consciously have to identify where you want to click, scroll to the position, etc. As most workflows usually happen within a menu group, having it extended when you are in a view inside that menu group would help with that.

Database changes

No response

External dependencies

No response

Originally created by @tomaskir on GitHub (Jul 23, 2021). ### NetBox version 3.0 ### Feature type New functionality ### Proposed functionality Menu should not close each time you change a view. It makes navigation a bit tedious. For example, when in the `Racks` view (and its subviews), keep the `Organization` section of the menu should stay extended. ### Use case Menu in 2.11 has no animations (faster navigation) and the menus groups being horizontally side-by-side makes visually identifying where things are faster - building "visual memory" for where to click to get to a particular view is quite easy due to the static positioning and each element having unique position is easier. In 3.0, due to animations and everything being in the same vertical menu (with dynamic position due to scroll), it means you consciously have to identify where you want to click, scroll to the position, etc. As most workflows usually happen within a menu group, having it extended when you are in a view inside that menu group would help with that. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerbeta labels 2025-12-29 19:24:11 +01:00
adam closed this issue 2025-12-29 19:24:11 +01:00
adam commented 2025-12-29 19:24:11 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Jul 26, 2021):

I'm not a fan of the new side menu either... Those to dropdown menu have a much faster to navigate and don't mess a round with the position you have to click...
The side menu also takes up space. Most output are tables, where we need the full width of the screen to display..

@PieterL75 commented on GitHub (Jul 26, 2021): I'm not a fan of the new side menu either... Those to dropdown menu have a much faster to navigate and don't mess a round with the position you have to click... The side menu also takes up space. Most output are tables, where we need the full width of the screen to display..
adam commented 2025-12-29 19:24:11 +01:00
Author
Owner
Copy Link

@binaryoverload commented on GitHub (Jul 28, 2021):

I do like the new menu but I do agree that it does take up a fair bit of space. Perhaps a good solution to this is to make the sidebar collapsible 🤔

@binaryoverload commented on GitHub (Jul 28, 2021): I do like the new menu but I do agree that it does take up a fair bit of space. Perhaps a good solution to this is to make the sidebar collapsible 🤔
adam commented 2025-12-29 19:24:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 29, 2021):

The tricky part is passing state to the menu, to know which section (if any) should be expanded. We actually did this in much older versions of NetBox to highlight the "active" menu button, but decided it wasn't worth the effort to keep up. I'd like to come up with something a bit more clever than manually specifying the active menu section under each view.

I'm not a fan of the new side menu either...

FWIW I ran a very informal Twitter poll where people preferred a sidebar to a top menu roughly 2:1. I imagine it will start to feel more familiar after a bit of use.

@jeremystretch commented on GitHub (Jul 29, 2021): The tricky part is passing state to the menu, to know which section (if any) should be expanded. We actually did this in much older versions of NetBox to highlight the "active" menu button, but decided it wasn't worth the effort to keep up. I'd like to come up with something a bit more clever than manually specifying the active menu section under each view. > I'm not a fan of the new side menu either... FWIW I ran a very informal [Twitter poll](https://twitter.com/jstretch85/status/1412743433681313792) where people preferred a sidebar to a top menu roughly 2:1. I imagine it will start to feel more familiar after a bit of use.
adam commented 2025-12-29 19:24:12 +01:00
Author
Owner
Copy Link

@thatmattlove commented on GitHub (Jul 30, 2021):

FYI, this is fixed as of 3752cb3. The nav menu is now collapsible and determines the state of the current page and highlights the appropriate menu item accordingly.

@thatmattlove commented on GitHub (Jul 30, 2021): FYI, this is fixed as of 3752cb3. The nav menu is now collapsible and determines the state of the current page and highlights the appropriate menu item accordingly.
adam commented 2025-12-29 19:24:12 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Aug 2, 2021):

What I don't like about sidebars, is that menu Items get dropped off the screen.
If you open 'device's, then you have to close it again before you can go to 'other/reports'.
No, this is not an improvement.

Navigation has to be quick without extra clicks to find your way

I can understand that the sidebar remains, but that the submenu pops out to the right, as it poped out to the bottom with the top menu. Then the navigation will be more slick

Pieter

@PieterL75 commented on GitHub (Aug 2, 2021): What I don't like about sidebars, is that menu Items get dropped off the screen. If you open 'device's, then you have to close it again before you can go to 'other/reports'. No, this is not an improvement. Navigation has to be quick without extra clicks to find your way I can understand that the sidebar remains, but that the submenu pops out to the right, as it poped out to the bottom with the top menu. Then the navigation will be more slick Pieter
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label beta status: needs owner type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5094
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?