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

slim-select-pagination-bug : user not able to load more than one page of data after a text search in slim select search box #9569

New Issue
Closed
opened 2025-12-29 21:19:04 +01:00 by adam · 6 comments
adam commented 2025-12-29 21:19:04 +01:00
Owner
Copy Link

Originally created by @MaxBear on GitHub (May 2, 2024).

Originally assigned to: @MaxBear on GitHub.

Deployment Type

NetBox Cloud

NetBox Version

v3.7.7-dev

Python Version

3.11

Steps to Reproduce

  1. insert enough entries in extras_tag table such that for a search string "x" there are more than 50 (default max page size) items returned
  2. open edit page for a dcim device interface
  3. open tag dialogue box which uses a slim select GUI control under the hood, enter search string "x" in the filter search box
  4. scroll down to the bottom of the returned list
  5. notice you cannot get more items behind the first page of returned items although an api call to the next page is already made

Expected Behavior

When user reaches the end of currently returned list of items more items will be extended to the list if there are more.

Observed Behavior

Current behaviour is that user will not be able to go behind the first page of returned items.

Originally created by @MaxBear on GitHub (May 2, 2024). Originally assigned to: @MaxBear on GitHub. ### Deployment Type NetBox Cloud ### NetBox Version v3.7.7-dev ### Python Version 3.11 ### Steps to Reproduce 1. insert enough entries in extras_tag table such that for a search string "x" there are more than 50 (default max page size) items returned 2. open edit page for a dcim device interface 3. open tag dialogue box which uses a slim select GUI control under the hood, enter search string "x" in the filter search box 4. scroll down to the bottom of the returned list 5. notice you cannot get more items behind the first page of returned items although an api call to the next page is already made ### Expected Behavior When user reaches the end of currently returned list of items more items will be extended to the list if there are more. ### Observed Behavior Current behaviour is that user will not be able to go behind the first page of returned items.
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:19:04 +01:00
adam closed this issue 2025-12-29 21:19:04 +01:00
adam commented 2025-12-29 21:19:05 +01:00
Author
Owner
Copy Link

@MaxBear commented on GitHub (May 2, 2024):

correction: the deployment type is self-hosted

@MaxBear commented on GitHub (May 2, 2024): correction: the deployment type is `self-hosted`
adam commented 2025-12-29 21:19:05 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 2, 2024):

@MaxBear I see you have a PR in for this so assigning it to you.

@arthanson commented on GitHub (May 2, 2024): @MaxBear I see you have a PR in for this so assigning it to you.
adam commented 2025-12-29 21:19:05 +01:00
Author
Owner
Copy Link

@MaxBear commented on GitHub (May 2, 2024):

Thanks @arthanson have you had a chance to code review my pr ?

@MaxBear commented on GitHub (May 2, 2024): Thanks @arthanson have you had a chance to code review my pr ?
adam commented 2025-12-29 21:19:05 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 2, 2024):

Actually @MaxBear this library has been completely removed in NB v4, so this would no longer apply. Going to close this.

@arthanson commented on GitHub (May 2, 2024): Actually @MaxBear this library has been completely removed in NB v4, so this would no longer apply. Going to close this.
adam commented 2025-12-29 21:19:05 +01:00
Author
Owner
Copy Link

@MaxBear commented on GitHub (May 3, 2024):

@arthanson we are still on v.3.4.10 for our netbox installation. Will my fix still be looked at and included in a patch release ?

@MaxBear commented on GitHub (May 3, 2024): @arthanson we are still on v.3.4.10 for our netbox installation. Will my [fix ](https://github.com/netbox-community/netbox/pull/15918) still be looked at and included in a patch release ?
adam commented 2025-12-29 21:19:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 3, 2024):

Re-opening this for review as it looks like we'll end up cutting a v3.7.8 release for some unrelated bug fixes.

@jeremystretch commented on GitHub (May 3, 2024): Re-opening this for review as it looks like we'll end up cutting a v3.7.8 release for some unrelated bug fixes.
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 severity: low status: accepted 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#9569
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?