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

Create duplicate [update], [create] and [cancel] button at the top of the page #1840

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

Originally created by @SandMouse on GitHub (Jul 13, 2018).

As a new user to this very helpful software I find my self scrolling down to the bottom of the page to click [create], [update] or [cancel] (etc, etc) many times a day. Since I'm still trying to find my way in and around this software I keep making many, many -small- changes. Mainly to the fields in the first part of different pages. After those changed I need to scroll down and choose a command to finish my input. E.g. [create], [update] or [cancel]. Would it be possible to add a duplicate set of buttons one can find at the bottom of the page, at the top of the page? See attached mock-up.
screen_shot_2018-07-13_at_15_51_28

Originally created by @SandMouse on GitHub (Jul 13, 2018). As a new user to this very helpful software I find my self scrolling down to the bottom of the page to click [create], [update] or [cancel] (etc, etc) many times a day. Since I'm still trying to find my way in and around this software I keep making many, many -small- changes. Mainly to the fields in the first part of different pages. After those changed I need to scroll down and choose a command to finish my input. E.g. [create], [update] or [cancel]. Would it be possible to add a duplicate set of buttons one can find at the bottom of the page, at the top of the page? See attached mock-up. ![screen_shot_2018-07-13_at_15_51_28](https://user-images.githubusercontent.com/5917501/42695367-80b12ca8-86b5-11e8-9071-63ad68228184.jpg)
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 17:19:39 +01:00
adam closed this issue 2025-12-29 17:19:40 +01:00
adam commented 2025-12-29 17:19:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 23, 2018):

Buttons are included only at the bottom to ensure that the user sees the entire form. Not sure about adding a duplicate set of buttons. How about moving the buttons to a fixed position to the right of the edit form, so that the buttons stay in one place as the user scrolls?

@jeremystretch commented on GitHub (Jul 23, 2018): Buttons are included only at the bottom to ensure that the user sees the entire form. Not sure about adding a duplicate set of buttons. How about moving the buttons to a fixed position to the right of the edit form, so that the buttons stay in one place as the user scrolls?
adam commented 2025-12-29 17:19:41 +01:00
Author
Owner
Copy Link

@mmahacek commented on GitHub (Jul 23, 2018):

I like the idea of floating buttons. I would not need buttons at the top when creating a new item as much as they would help modifying an existing item.

@mmahacek commented on GitHub (Jul 23, 2018): I like the idea of floating buttons. I would not need buttons at the top when creating a new item as much as they would help modifying an existing item.
adam commented 2025-12-29 17:19:41 +01:00
Author
Owner
Copy Link

@hellerve commented on GitHub (May 29, 2019):

While this generally seems to work just fine, this will break the responsiveness of the site. Once the page width is under certain threshold, the form takes up the whole width of the page. Making the buttons float would make them float over the form. So I guess this type of fix will in fact only affect people who use Netbox on their desktop computer with the window larger than a certain width (992px seems to be the magic number).

This is good enough for me, but I’m not sure whether this is congruent to the fix that was originally envisioned.

@hellerve commented on GitHub (May 29, 2019): While this generally seems to work just fine, this will break the responsiveness of the site. Once the page width is under certain threshold, the form takes up the whole width of the page. Making the buttons float would make them float over the form. So I guess this type of fix will in fact only affect people who use Netbox on their desktop computer with the window larger than a certain width (992px seems to be the magic number). This is good enough for me, but I’m not sure whether this is congruent to the fix that was originally envisioned.
adam commented 2025-12-29 17:19:41 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 7, 2020):

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.

@stale[bot] commented on GitHub (Sep 7, 2020): 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 17:19:41 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 23, 2020):

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.

@stale[bot] commented on GitHub (Sep 23, 2020): 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#1840
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?