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

Add additional save / create / cancel buttons to top of forms (or make existing buttons stay visible) #9609

New Issue
Closed
opened 2025-12-29 21:19:40 +01:00 by adam · 9 comments
adam commented 2025-12-29 21:19:40 +01:00
Owner
Copy Link

Originally created by @ITJamie on GitHub (May 7, 2024).

Originally assigned to: @atownson on GitHub.

NetBox version

v4.0.0

Feature type

New functionality

Proposed functionality

Add save / create / cancel buttons to top of forms (or make existing buttons stay visible )

Use case

when a model has a lot of fields/custom fields (or is being used on a small display) there can be a lot of scrolling to get to the save / create buttons.
it would be great if there was a copy of those buttons at the top of the form or if the existing buttons were always visible on the form

Database changes

N/A

External dependencies

N/A

Originally created by @ITJamie on GitHub (May 7, 2024). Originally assigned to: @atownson on GitHub. ### NetBox version v4.0.0 ### Feature type New functionality ### Proposed functionality Add `save / create / cancel` buttons to top of forms (or make existing buttons stay visible ) ### Use case when a model has a lot of fields/custom fields (or is being used on a small display) there can be a lot of scrolling to get to the save / create buttons. it would be great if there was a copy of those buttons at the top of the form or if the existing buttons were always visible on the form ### Database changes N/A ### External dependencies N/A
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:19:40 +01:00
adam closed this issue 2025-12-29 21:19:40 +01:00
adam commented 2025-12-29 21:19:41 +01:00
Author
Owner
Copy Link

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

There was some discussion around this idea way back in #2237. Unfortunately it never found an owner.

@jeremystretch commented on GitHub (May 7, 2024): There was some discussion around this idea way back in #2237. Unfortunately it never found an owner.
adam commented 2025-12-29 21:19:41 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (May 7, 2024):

What would be deemed acceptable?

  • An extra set of buttons at the top of the form
  • Some kind of "fixed" bar with the action buttons

If it was just an extra set of buttons at the top I could likely take a stab at it.

@ITJamie commented on GitHub (May 7, 2024): What would be deemed acceptable? - An extra set of buttons at the top of the form - Some kind of "fixed" bar with the action buttons If it was just an extra set of buttons at the top I could likely take a stab at it.
adam commented 2025-12-29 21:19:41 +01:00
Author
Owner
Copy Link

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

IMO a single set of fixed/floating buttons would be ideal. Rendering multiple buttons that do the same thing can be confusing and error-prone.

@jeremystretch commented on GitHub (May 7, 2024): IMO a single set of fixed/floating buttons would be ideal. Rendering multiple buttons that do the same thing can be confusing and error-prone.
adam commented 2025-12-29 21:19:42 +01:00
Author
Owner
Copy Link

@paynl-wesley commented on GitHub (May 22, 2024):

What would be deemed acceptable?

  • An extra set of buttons at the top of the form
  • Some kind of "fixed" bar with the action buttons

If it was just an extra set of buttons at the top I could likely take a stab at it.

IMHO a fixed bar with the action buttons on the bottom would be awesome!

@paynl-wesley commented on GitHub (May 22, 2024): > What would be deemed acceptable? > > * An extra set of buttons at the top of the form > * Some kind of "fixed" bar with the action buttons > > If it was just an extra set of buttons at the top I could likely take a stab at it. IMHO a fixed bar with the action buttons on the bottom would be awesome!
adam commented 2025-12-29 21:19:42 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 27, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 27, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 21:19:42 +01:00
Author
Owner
Copy Link

@atownson commented on GitHub (Sep 16, 2024):

Any thoughts on this approach?

Added this CSS to the buttons div:

position: sticky;
bottom: 0px;
padding: 2px 0px 10px 0px;
z-index: 1;
background-color: var(--tblr-bg-surface-tertiary)

Result:

https://github.com/user-attachments/assets/4e230529-82ab-4641-a677-e3399af5c637

@atownson commented on GitHub (Sep 16, 2024): Any thoughts on this approach? Added this CSS to the buttons div: ``` position: sticky; bottom: 0px; padding: 2px 0px 10px 0px; z-index: 1; background-color: var(--tblr-bg-surface-tertiary) ``` Result: https://github.com/user-attachments/assets/4e230529-82ab-4641-a677-e3399af5c637
adam commented 2025-12-29 21:19:42 +01:00
Author
Owner
Copy Link

@paynl-wesley commented on GitHub (Sep 17, 2024):

Awesome!

@paynl-wesley commented on GitHub (Sep 17, 2024): Awesome!
adam commented 2025-12-29 21:19:42 +01:00
Author
Owner
Copy Link

@atownson commented on GitHub (Sep 17, 2024):

I can submit a PR for this if the above method is acceptable.

@atownson commented on GitHub (Sep 17, 2024): I can submit a PR for this if the above method is acceptable.
adam commented 2025-12-29 21:19:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 17, 2024):

Thanks @atownson I've assigned this to you for a PR.

@jeremystretch commented on GitHub (Sep 17, 2024): Thanks @atownson I've assigned this to you for a PR.
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: low status: accepted 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#9609
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?