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

[PR #6799] [CLOSED] style(sidebar): fix sidebar dual scroll contexts #13174

New Issue
Closed
opened 2025-12-29 22:25:48 +01:00 by adam · 0 comments
adam commented 2025-12-29 22:25:48 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/netbox-community/netbox/pull/6799
Author: @ndom91
Created: 7/23/2021
Status: ❌ Closed

Base: feature ← Head: patch-1

📝 Commits (1)

  • 0bb6c89 Update netbox.scss - fix sidebar dual scroll contexts

📊 Changes

1 file changed (+1 additions, -2 deletions)

View changed files

📝 netbox/project-static/styles/netbox.scss (+1 -2)

📄 Description

Fixes:

Currently large sections, like IPAM, create new scroll contexts inside themselves.

image

I think its more standard to fully open the dropdown and just scroll it with the master list of categories, i.e. extending the original scroll context.

Sorry, wasn't sure if you were going against feature or develop at the moment..

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbox-community/netbox/pull/6799 **Author:** [@ndom91](https://github.com/ndom91) **Created:** 7/23/2021 **Status:** ❌ Closed **Base:** `feature` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`0bb6c89`](https://github.com/netbox-community/netbox/commit/0bb6c89268f67a5b8271457a2e5a3d7567c9aab7) Update netbox.scss - fix sidebar dual scroll contexts ### 📊 Changes **1 file changed** (+1 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `netbox/project-static/styles/netbox.scss` (+1 -2) </details> ### 📄 Description <!-- Thank you for your interest in contributing to NetBox! Please note that our contribution policy requires that a feature request or bug report be opened for approval prior to filing a pull request. This helps avoid wasting time and effort on something that we might not be able to accept. Please indicate the relevant feature request or bug report below. IF YOUR PULL REQUEST DOES NOT REFERENCE AN ACCEPTED BUG REPORT OR FEATURE REQUEST, IT WILL BE MARKED AS INVALID AND CLOSED. --> ### Fixes: <ISSUE NUMBER GOES HERE> <!-- Please include a summary of the proposed changes below. --> Currently large sections, like IPAM, create new scroll contexts inside themselves. ![image](https://user-images.githubusercontent.com/7415984/126805914-10ad9da5-a0c1-4edc-aa8a-25cc4dae7b03.png) I think its more standard to fully open the dropdown and just scroll it with the master list of categories, i.e. extending the original scroll context. Sorry, wasn't sure if you were going against `feature` or `develop` at the moment.. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 22:25:48 +01:00
adam closed this issue 2025-12-29 22:25:48 +01:00
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 pull-request
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#13174
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?