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

UI Change for button placement in panels #369

New Issue
Closed
opened 2025-12-29 16:21:23 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:21:23 +01:00
Owner
Copy Link

Originally created by @WilliamMarti on GitHub (Aug 16, 2016).

So it looks like the normal convention for button placement in panels is in the panel-footer in Netbox. For most areas this isn't a big deal, but the 'Interfaces' panel for Devices gets rather lengthy for some larger chassis based switches. It seems to be a fairly established UI convention to have buttons placed at the top of the resource they control.

Here is an example of what I am thinking:

capture

Now I don't have to scroll to the bottom of the page to make additions or delete selected interfaces. This also might be a good place for a "Select All" checkbox as well.

I wouldn't mind making this change, but wanted your(stretch) opinion first

Originally created by @WilliamMarti on GitHub (Aug 16, 2016). So it looks like the normal convention for button placement in panels is in the panel-footer in Netbox. For most areas this isn't a big deal, but the 'Interfaces' panel for Devices gets rather lengthy for some larger chassis based switches. It seems to be a fairly established UI convention to have buttons placed at the top of the resource they control. Here is an example of what I am thinking: ![capture](https://cloud.githubusercontent.com/assets/4473602/17708146/b49c3036-63b1-11e6-9cca-a8374f3cbde5.PNG) Now I don't have to scroll to the bottom of the page to make additions or delete selected interfaces. This also might be a good place for a "Select All" checkbox as well. I wouldn't mind making this change, but wanted your(stretch) opinion first
adam added the type: feature label 2025-12-29 16:21:23 +01:00
adam closed this issue 2025-12-29 16:21:24 +01:00
adam commented 2025-12-29 16:21:24 +01:00
Author
Owner
Copy Link

@sts commented on GitHub (Sep 16, 2016):

-1 on how this currently looks like.

I feel the buttons would rather be placed on the right side. 'Add interface' right to 'delete interface' button and the padding between those should be fixed too.

@sts commented on GitHub (Sep 16, 2016): -1 on how this currently looks like. I feel the buttons would rather be placed on the right side. 'Add interface' right to 'delete interface' button and the padding between those should be fixed too.
adam commented 2025-12-29 16:21:24 +01:00
Author
Owner
Copy Link

@WilliamMarti commented on GitHub (Sep 21, 2016):

I would be fine with having the buttons right aligned. I think the greater issue is moving the buttons to the top of the resouce

@WilliamMarti commented on GitHub (Sep 21, 2016): I would be fine with having the buttons right aligned. I think the greater issue is moving the buttons to the top of the resouce
adam commented 2025-12-29 16:21:25 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 28, 2016):

The "add <object>" buttons are now displayed in the bottom right corner of all device and device type component panels. The are also displayed in the top right corner if the panel contains more than ten objects.

@jeremystretch commented on GitHub (Sep 28, 2016): The "add &lt;object&gt;" buttons are now displayed in the bottom right corner of all device and device type component panels. The are also displayed in the top right corner if the panel contains more than ten objects.
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 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#369
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?