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

Return the slim sidebar menu #9427

New Issue
Closed
opened 2025-12-29 20:49:46 +01:00 by adam · 16 comments
adam commented 2025-12-29 20:49:46 +01:00
Owner
Copy Link

Originally created by @julianstolp on GitHub (Apr 4, 2024).

NetBox version

v4.0-beta1

Feature type

Change to existing functionality

Proposed functionality

The new sidebar is wider and there is no possiblity to hide this massive sidebar.
Proposed change:
Some sticky icon like in the old UI
image
image

Use case

Use the screen more efficiently and prevent/minimize horizontal scrolling in tables.

Database changes

External dependencies

Originally created by @julianstolp on GitHub (Apr 4, 2024). ### NetBox version v4.0-beta1 ### Feature type Change to existing functionality ### Proposed functionality The new sidebar is wider and there is no possiblity to hide this massive sidebar. Proposed change: Some sticky icon like in the old UI ![image](https://github.com/netbox-community/netbox/assets/41152397/006c4eb4-e05b-4061-820c-dbf72b68e533) ![image](https://github.com/netbox-community/netbox/assets/41152397/384c8cef-e079-4ea2-8f4b-56379f651410) ### Use case Use the screen more efficiently and prevent/minimize horizontal scrolling in tables. ### Database changes - ### External dependencies -
adam added the type: featurecomplexity: mediumtopic: UI/UX labels 2025-12-29 20:49:46 +01:00
adam closed this issue 2025-12-29 20:49:46 +01:00
adam commented 2025-12-29 20:49:47 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 4, 2024):

IMO the collapsed navigation menu in v3 is unnecessary and, when not stickied, rather annoying. I've been using the current UI for months on a relatively narrow (1280px) viewport without issue. I see no reason to retain the old functionality, but will leave this open for discussion if someone else would like to own it.

@jeremystretch commented on GitHub (Apr 4, 2024): IMO the collapsed navigation menu in v3 is unnecessary and, when not stickied, rather annoying. I've been using the current UI for months on a relatively narrow (1280px) viewport without issue. I see no reason to retain the old functionality, but will leave this open for discussion if someone else would like to own it.
adam commented 2025-12-29 20:49:48 +01:00
Author
Owner
Copy Link

@julianstolp commented on GitHub (Apr 4, 2024):

We have almost exclusively used the narrow navigation bar to display as many columns as possible. It would be nice if this option were available again.

@julianstolp commented on GitHub (Apr 4, 2024): We have almost exclusively used the narrow navigation bar to display as many columns as possible. It would be nice if this option were available again.
adam commented 2025-12-29 20:49:48 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Apr 4, 2024):

I also would like to see the collapsed navigation bar return. The new one is 33px wider than even the fully expanded one before and 241px wider than the collapsed one. When you are displaying a table with a lot of columns, every pixel helps. The worst offender for me is usually the Interfaces table, where I find it difficult to fit all the columns I need even on a 2560px wide screen.

I can tell you from experience with my end users that they have always been thrilled when I show them the ability to collapse the menu and get some valuable screen real estate back. From observation, the menu is almost never used in our environment, so even the collapsed version has been identified as an annoyance. The typical flow I see is users finding what they are looking for through the global search, then navigating around from there through breadcrumbs or other links within the view. In fact, most of my users don't even know where to find things in the menu because of how infrequently they use it.

@sleepinggenius2 commented on GitHub (Apr 4, 2024): I also would like to see the collapsed navigation bar return. The new one is 33px wider than even the fully expanded one before and 241px wider than the collapsed one. When you are displaying a table with a lot of columns, every pixel helps. The worst offender for me is usually the Interfaces table, where I find it difficult to fit all the columns I need even on a 2560px wide screen. I can tell you from experience with my end users that they have always been thrilled when I show them the ability to collapse the menu and get some valuable screen real estate back. From observation, the menu is almost never used in our environment, so even the collapsed version has been identified as an annoyance. The typical flow I see is users finding what they are looking for through the global search, then navigating around from there through breadcrumbs or other links within the view. In fact, most of my users don't even know where to find things in the menu because of how infrequently they use it.
adam commented 2025-12-29 20:49:48 +01:00
Author
Owner
Copy Link

@petersonbasso commented on GitHub (Apr 8, 2024):

The collapsed navigation menu is very useful, especially for small screens.
Better to keep the option and leave it up to the user to keep it fixed.

@petersonbasso commented on GitHub (Apr 8, 2024): The collapsed navigation menu is very useful, especially for small screens. Better to keep the option and leave it up to the user to keep it fixed.
adam commented 2025-12-29 20:49:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 8, 2024):

Opening this for a volunteer to implement it.

@jeremystretch commented on GitHub (Apr 8, 2024): Opening this for a volunteer to implement it.
adam commented 2025-12-29 20:49:49 +01:00
Author
Owner
Copy Link

@julianstolp commented on GitHub (Apr 9, 2024):

If someone is able to implement this, there is an open FR in the Tabler repository. It would certainly be good to implement this there so that no/less custom code is necessary in NetBox.

https://github.com/tabler/tabler/issues/1803

@julianstolp commented on GitHub (Apr 9, 2024): If someone is able to implement this, there is an open FR in the Tabler repository. It would certainly be good to implement this there so that no/less custom code is necessary in NetBox. https://github.com/tabler/tabler/issues/1803
adam commented 2025-12-29 20:49:49 +01:00
Author
Owner
Copy Link

@heroin-moose commented on GitHub (May 14, 2024):

Please, please, please, please, please, please, please, please, please bring it back.

@heroin-moose commented on GitHub (May 14, 2024): Please, please, please, please, please, please, please, please, please bring it back.
adam commented 2025-12-29 20:49:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 14, 2024):

@heroin-moose would you like to take ownership of this issue?

@jeremystretch commented on GitHub (May 14, 2024): @heroin-moose would you like to take ownership of this issue?
adam commented 2025-12-29 20:49:49 +01:00
Author
Owner
Copy Link

@heroin-moose commented on GitHub (May 14, 2024):

@jeremystretch, yeah, why not. Would you prefer it solved via https://github.com/tabler/tabler/issues/1803?

@heroin-moose commented on GitHub (May 14, 2024): @jeremystretch, yeah, why not. Would you prefer it solved via https://github.com/tabler/tabler/issues/1803?
adam commented 2025-12-29 20:49:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 14, 2024):

Upstream support would be strongly preferred, but of course that's out of our control. We'd only accept a local implementation if it can be achieved in a clean, maintainable manner with minimal additional code.

@jeremystretch commented on GitHub (May 14, 2024): Upstream support would be strongly preferred, but of course that's out of our control. We'd only accept a local implementation if it can be achieved in a clean, maintainable manner with minimal additional code.
adam commented 2025-12-29 20:49:50 +01:00
Author
Owner
Copy Link

@heroin-moose commented on GitHub (May 14, 2024):

I'll do my best.

@heroin-moose commented on GitHub (May 14, 2024): I'll do my best.
adam commented 2025-12-29 20:49:50 +01:00
Author
Owner
Copy Link

@bobbwest commented on GitHub (May 27, 2024):

An interim solution would be to have a toggle that would disable the responsive full side navbar menu, keeping the dropdown navbar menu that is usually activated on narrow viewports. At least that means people wanting a wide tabular display can achieve that, and still maintain some access to the navbar menu.

@bobbwest commented on GitHub (May 27, 2024): An interim solution would be to have a toggle that would disable the responsive full side navbar menu, keeping the dropdown navbar menu that is usually activated on narrow viewports. At least that means people wanting a wide tabular display can achieve that, and still maintain some access to the navbar menu.
adam commented 2025-12-29 20:49:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 28, 2024):

@heroin-moose are you still planning to work on this, or should we release it for another volunteer?

@jeremystretch commented on GitHub (May 28, 2024): @heroin-moose are you still planning to work on this, or should we release it for another volunteer?
adam commented 2025-12-29 20:49:51 +01:00
Author
Owner
Copy Link

@heroin-moose commented on GitHub (May 29, 2024):

I'm slowly getting there, but if someone gets there first I would gladly pass the issue. I have a PoC that mostly works, I will fix the remaining issues I see and submit it to Tabler.

@heroin-moose commented on GitHub (May 29, 2024): I'm slowly getting there, but if someone gets there first I would gladly pass the issue. I have a PoC that mostly works, I will fix the remaining issues I see and submit it to Tabler.
adam commented 2025-12-29 20:49:51 +01:00
Author
Owner
Copy Link

@PaulR282 commented on GitHub (Jun 13, 2024):

This feature would be highly appreciated because the sidebar uses a lot of space on small displays.

@PaulR282 commented on GitHub (Jun 13, 2024): This feature would be highly appreciated because the sidebar uses a lot of space on small displays.
adam commented 2025-12-29 20:49:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 20, 2024):

I'm going to close this in favor of #16392, which is being actively worked locally by @andrewgormley. Hopefully we'll be able to leverage @heroin-moose's upstream contribution to Tabler at some point in the future.

@jeremystretch commented on GitHub (Jun 20, 2024): I'm going to close this in favor of #16392, which is being actively worked locally by @andrewgormley. Hopefully we'll be able to leverage @heroin-moose's upstream contribution to Tabler at some point in the future.
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 complexity: medium topic: UI/UX 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#9427
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?