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

Search field scrolls off-screen #9521

New Issue
Closed
opened 2025-12-29 20:50:56 +01:00 by adam · 5 comments
adam commented 2025-12-29 20:50:56 +01:00
Owner
Copy Link

Originally created by @PieterL75 on GitHub (Apr 23, 2024).

Deployment Type

NetBox Cloud

NetBox Version

v4.0-beta1

Python Version

3.8

Steps to Reproduce

Scroll down on a page that has many lines

Expected Behavior

The searchbar remains accessible at all times

Observed Behavior

The searchbar scrolls offscreen

Originally created by @PieterL75 on GitHub (Apr 23, 2024). ### Deployment Type NetBox Cloud ### NetBox Version v4.0-beta1 ### Python Version 3.8 ### Steps to Reproduce Scroll down on a page that has many lines ### Expected Behavior The searchbar remains accessible at all times ### Observed Behavior The searchbar scrolls offscreen
adam added the type: bugstatus: revisions neededbeta labels 2025-12-29 20:50:56 +01:00
adam closed this issue 2025-12-29 20:50:56 +01:00
adam commented 2025-12-29 20:50:56 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Apr 23, 2024):

Hi Pieter, thanks for the report. I see some inconsistencies in your report that need correcting before we can attempt to reproduce this problem:

  • 4.0 betas are not yet available on NetBox Cloud, so I think your deployment type is incorrect
  • Python 3.8 is not supported in NetBox 4.0, so if that's the version you're in fact using, we need to know whether you still see the problem with Python 3.10 or later.

Please revise the issue body accordingly.

@jeffgdotorg commented on GitHub (Apr 23, 2024): Hi Pieter, thanks for the report. I see some inconsistencies in your report that need correcting before we can attempt to reproduce this problem: - 4.0 betas are not yet available on NetBox Cloud, so I think your deployment type is incorrect - Python 3.8 is [not supported in NetBox 4.0](https://github.com/netbox-community/netbox/blob/feature/docs/installation/index.md#requirements), so if that's the version you're in fact using, we need to know whether you still see the problem with Python 3.10 or later. Please revise the issue body accordingly.
adam commented 2025-12-29 20:50:57 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Apr 23, 2024):

On second reading, this issue appears to describe a feature request rather than a bug. Sticky-scroll behavior for the search box was intentionally omitted from the initial 4.0 scope in the interest of velocity.

It's valuable to know that somebody is paying attention to that aspect of the UI. If you'll reopen this issue as a feature request, we'll get the work scheduled to bring that behavior back when capacity permits.

@jeffgdotorg commented on GitHub (Apr 23, 2024): On second reading, this issue appears to describe a feature request rather than a bug. Sticky-scroll behavior for the search box was intentionally omitted from the initial 4.0 scope in the interest of velocity. It's valuable to know that somebody is paying attention to that aspect of the UI. If you'll reopen this issue as a feature request, we'll get the work scheduled to bring that behavior back when capacity permits.
adam commented 2025-12-29 20:50:57 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Apr 24, 2024):

How can this be an improvement to remove the most used field of netbox out of the screen ?
this is bug/oversight...

And I don't like that you all just close these reports, in stead of taking them serious and swap them to a 'feature request'.
I try to help you, and point out something. Have it closed is really counter-helpfull and probably just stop me of submitting more things that are differente in v4 then in v3.

@PieterL75 commented on GitHub (Apr 24, 2024): How can this be an improvement to remove the most used field of netbox out of the screen ? this is bug/oversight... And I don't like that you all just close these reports, in stead of taking them serious and swap them to a 'feature request'. I try to help you, and point out something. Have it closed is really counter-helpfull and probably just stop me of submitting more things that are differente in v4 then in v3.
adam commented 2025-12-29 20:50:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 24, 2024):

this is bug/oversight

It's not. It was a conscious decision not to use a fixed top menu.

And I don't like that you all just close these reports, in stead of taking them serious and swap them to a 'feature request'.

Submitting a feature request requires different information not provided above, which is why it has a separate issue template. Bug reports are to be used only when addressing behavior that differs from what was intended by the developer, not from what you would prefer.

I try to help you, and point out something. Have it closed is really counter-helpfull and probably just stop me of submitting more things that are differente in v4 then in v3.

Please use the correct issue templates when doing so. Misusing the forms only adds to the ever-increasing burden of maintaining the project.

@jeremystretch commented on GitHub (Apr 24, 2024): > this is bug/oversight It's not. It was a conscious decision not to use a fixed top menu. > And I don't like that you all just close these reports, in stead of taking them serious and swap them to a 'feature request'. Submitting a feature request requires different information not provided above, which is why it has a separate issue template. Bug reports are to be used only when addressing behavior that differs from what was intended by the developer, _not_ from what you would prefer. > I try to help you, and point out something. Have it closed is really counter-helpfull and probably just stop me of submitting more things that are differente in v4 then in v3. Please use the correct issue templates when doing so. Misusing the forms only adds to the ever-increasing burden of maintaining the project.
adam commented 2025-12-29 20:50:57 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Apr 24, 2024):

I don't see that this was mentioned in the UI overhaul..
https://github.com/netbox-community/netbox/issues/12128
so assuming it was an oversight or something that is not functioning as it was before 4.0

I'll submit FR for all other in the future (but please dont close if they are bugs :-)

@PieterL75 commented on GitHub (Apr 24, 2024): I don't see that this was mentioned in the UI overhaul.. https://github.com/netbox-community/netbox/issues/12128 so assuming it was an oversight or something that is not functioning as it was before 4.0 I'll submit FR for all other in the future (but please dont close if they are bugs :-)
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 beta status: revisions needed type: bug
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#9521
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?