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

Save button on top #5456

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

Originally created by @rfl64 on GitHub (Oct 1, 2021).

NetBox version

v3.0.4

Feature type

Change to existing functionality

Proposed functionality

Would be possible locate Save and other buttons that are at the bottom of the page at top position?

Use case

Every device, interface, etc, when I want to save I must use vertical bar to move page from top to bottom to save.

thanks in advance.

Database changes

No response

External dependencies

No response

Originally created by @rfl64 on GitHub (Oct 1, 2021). ### NetBox version v3.0.4 ### Feature type Change to existing functionality ### Proposed functionality Would be possible locate Save and other buttons that are at the bottom of the page at top position? ### Use case Every device, interface, etc, when I want to save I must use vertical bar to move page from top to bottom to save. thanks in advance. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:28:16 +01:00
adam closed this issue 2025-12-29 19:28:16 +01:00
adam commented 2025-12-29 19:28:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 5, 2021):

IMO this could lead to confusion. I'm also not sure where you would place the buttons to look natural.

@jeremystretch commented on GitHub (Oct 5, 2021): IMO this could lead to confusion. I'm also not sure where you would place the buttons to look natural.
adam commented 2025-12-29 19:28:17 +01:00
Author
Owner
Copy Link

@bluikko commented on GitHub (Oct 21, 2021):

I was just wondering about something similar while getting tired of scrolling down down down when editing several devices.

My proposal is that the Cancel and Save buttons "float" on the right side of the page when they wouldn't be visible otherwise (there is plenty of padding on the right side) - possibly organized vertically on top of each other when not at the bottom of the page. They should be always on the same place vertically, possible at the bottom right corner of the current viewport.

If the user has scrolled to the bottom of the page (i.e. the buttons would be visible) then the buttons move to the current positions.

Maybe it would be difficult to implement in which case copy of buttons at the top could be good.

@bluikko commented on GitHub (Oct 21, 2021): I was just wondering about something similar while getting tired of scrolling down down down when editing several devices. My proposal is that the `Cancel` and `Save` buttons "float" on the right side of the page when they wouldn't be visible otherwise (there is plenty of padding on the right side) - possibly organized vertically on top of each other when not at the bottom of the page. They should be always on the same place vertically, possible at the bottom right corner of the current viewport. If the user has scrolled to the bottom of the page (i.e. the buttons would be visible) then the buttons move to the current positions. Maybe it would be difficult to implement in which case copy of buttons at the top could be good.
adam commented 2025-12-29 19:28:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 21, 2021):

ISTR we've tried the fixed/floating effect in the past and never got it to work right. Maybe it's more feasible since the UI overhaul? I'll mark this as needs owner for anyone who would like to give it a shot.

@jeremystretch commented on GitHub (Oct 21, 2021): ISTR we've tried the fixed/floating effect in the past and never got it to work right. Maybe it's more feasible since the UI overhaul? I'll mark this as `needs owner` for anyone who would like to give it a shot.
adam commented 2025-12-29 19:28:17 +01:00
Author
Owner
Copy Link

@bluikko commented on GitHub (Oct 22, 2021):

By the way the same probably applies to the Edit selected and Delete selected buttons at the bottom of the page.

@bluikko commented on GitHub (Oct 22, 2021): By the way the same probably applies to the `Edit selected` and `Delete selected` buttons at the bottom of the page.
adam commented 2025-12-29 19:28:17 +01:00
Author
Owner
Copy Link

@bluikko commented on GitHub (Oct 31, 2021):

While having another session of scrolling up/down because of the Edit and Delete buttons I had an idea that could be one option - it does feel a bit strange though:

Could the "action buttons at the bottom of the page" be added to the bottom of the menu column at the left? Perhaps only visible when the buttons at the bottom of the page are not visible?

I.e. at the bottom left corner of the viewport. If the menu is "collapsed" to icons only, then it could show the "Edit" icon and "Delete" icon with the right button color (same as the buttons at the bottom of the page).

It does feel a bit like "abuse" of the menu but this would solve the button visibility/scrolling requirement issue in quite a nice way. If the "fixed/floating" buttons are difficult to implement then perhaps it could be an easy way too.

@bluikko commented on GitHub (Oct 31, 2021): While having another session of scrolling up/down because of the `Edit` and `Delete` buttons I had an idea that could be one option - it does feel a bit strange though: Could the "action buttons at the bottom of the page" be added to the bottom of the menu column at the left? Perhaps only visible when the buttons at the bottom of the page are not visible? I.e. at the bottom left corner of the viewport. If the menu is "collapsed" to icons only, then it could show the "Edit" icon and "Delete" icon with the right button color (same as the buttons at the bottom of the page). It does feel a bit like "abuse" of the menu but this would solve the button visibility/scrolling requirement issue in quite a nice way. If the "fixed/floating" buttons are difficult to implement then perhaps it could be an easy way too.
adam commented 2025-12-29 19:28:18 +01:00
Author
Owner
Copy Link

@rhyser9 commented on GitHub (Nov 12, 2021):

Something I just discovered that makes my life much easier, is that you can submit forms with the Enter key. Reduces the need to scroll down and hunt for the save button.

@rhyser9 commented on GitHub (Nov 12, 2021): Something I just discovered that makes my life much easier, is that you can submit forms with the Enter key. Reduces the need to scroll down and hunt for the save button.
adam commented 2025-12-29 19:28:18 +01:00
Author
Owner
Copy Link

@bluikko commented on GitHub (Nov 13, 2021):

Something I just discovered that makes my life much easier, is that you can submit forms with the Enter key. Reduces the need to scroll down and hunt for the save button.

Does not work always. For example try it in a field which input type is a drop-down box. And choose to edit a drop-down box that is surrounded by other drop-down boxes... I've opened #7667 about that.

Another reason is that there might be several buttons at the bottom. For example: "save & continue editing", "save", "cancel". Enter may use the first one, while the user might want the second. Or the other way round.

@bluikko commented on GitHub (Nov 13, 2021): > Something I just discovered that makes my life much easier, is that you can submit forms with the Enter key. Reduces the need to scroll down and hunt for the save button. Does not work always. For example try it in a field which input type is a drop-down box. And choose to edit a drop-down box that is surrounded by other drop-down boxes... I've opened #7667 about that. Another reason is that there might be several buttons at the bottom. For example: "save & continue editing", "save", "cancel". Enter may use the first one, while the user might want the second. Or the other way round.
adam commented 2025-12-29 19:28:18 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 12, 2022):

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. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jan 12, 2022): 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:28:18 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 11, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Feb 11, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure 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#5456
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?