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

Collapse page headers when scrolling down #10221

New Issue
Closed
opened 2025-12-29 21:28:31 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:28:31 +01:00
Owner
Copy Link

Originally created by @PieterL75 on GitHub (Sep 11, 2024).

NetBox version

v4.0

Feature type

New functionality

Proposed functionality

The top part of the page contains information about the model you are looking at.
When scrolling down, the model info should be retained in a smaller format.
Before scrolling :
image

After scrolling:
image

Use case

Having the name and breadcrumbs of the model visible helps

Database changes

No response

External dependencies

No response

Originally created by @PieterL75 on GitHub (Sep 11, 2024). ### NetBox version v4.0 ### Feature type New functionality ### Proposed functionality The top part of the page contains information about the model you are looking at. When scrolling down, the model info should be retained in a smaller format. Before scrolling : ![image](https://github.com/user-attachments/assets/5e79c019-ede1-4c11-bda5-6e2c7c82488d) After scrolling: ![image](https://github.com/user-attachments/assets/0df91882-af4f-4580-9f33-7e2f29a4a0e8) ### Use case Having the name and breadcrumbs of the model visible helps ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: under reviewnetbox labels 2025-12-29 21:28:31 +01:00
adam closed this issue 2025-12-29 21:28:31 +01:00
adam commented 2025-12-29 21:28:32 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Jan 23, 2025):

This is a good idea, but the proposal brings up the potential to add persistent / sticky header features for list views too — i.e. column headers that remain visible as you scroll down the table. This wouldn't be relevant on object detail views where the breadcrumbs are visible and relevant, but it would come into play on object-scoped list views like the one in the OP, where you would have both breadcrumbs and column headers as candidates for stickiness.

I think it's a good idea to add some dynamic scrolling behavior with a persistent sparse header, but let's give some thought to what would be the most useful (ideally unified across both detail and list views) set of features to have in that header. Otherwise once we start adding persistent header features (i.e. if we implement sticky breadcrumbs only) we're going to feel pressure to add more and more such functionality to it.

@bctiemann commented on GitHub (Jan 23, 2025): This is a good idea, but the proposal brings up the potential to add persistent / sticky header features for list views too — i.e. column headers that remain visible as you scroll down the table. This wouldn't be relevant on object detail views where the breadcrumbs are visible and relevant, but it would come into play on object-scoped list views like the one in the OP, where you would have both breadcrumbs _and_ column headers as candidates for stickiness. I think it's a good idea to add some dynamic scrolling behavior with a persistent sparse header, but let's give some thought to what would be the most useful (ideally unified across both detail and list views) set of features to have in that header. Otherwise once we start adding persistent header features (i.e. if we implement sticky breadcrumbs only) we're going to feel pressure to add more and more such functionality to it.
adam commented 2025-12-29 21:28:32 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Jan 24, 2025):

Looks like there are more requests on the UI, maybe indeed a good idea to gather them and combine

https://github.com/netbox-community/netbox/issues/12641
https://github.com/netbox-community/netbox/issues/9386
https://github.com/netbox-community/netbox/issues/15614
https://github.com/netbox-community/netbox/issues/18478 (just created)
https://github.com/netbox-community/netbox/discussions/17091

@PieterL75 commented on GitHub (Jan 24, 2025): Looks like there are more requests on the UI, maybe indeed a good idea to gather them and combine https://github.com/netbox-community/netbox/issues/12641 https://github.com/netbox-community/netbox/issues/9386 https://github.com/netbox-community/netbox/issues/15614 https://github.com/netbox-community/netbox/issues/18478 (just created) https://github.com/netbox-community/netbox/discussions/17091
adam commented 2025-12-29 21:28:33 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 25, 2025):

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 (Apr 25, 2025): 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/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:28:33 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 25, 2025):

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 (May 25, 2025): 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 netbox pending closure status: under review 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#10221
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?