Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the "pager" usable when browsing search results #1617

Open
1 task
pombredanne opened this issue Oct 16, 2024 · 4 comments
Open
1 task

Make the "pager" usable when browsing search results #1617

pombredanne opened this issue Oct 16, 2024 · 4 comments
Labels

Comments

@pombredanne
Copy link
Collaborator

pombredanne commented Oct 16, 2024

Shared by a shy user through a private email:

BTW, I just ran into the pager on Vulnerable Code, this could be improved:

https://public.vulnerablecode.io/packages/search?page=2&search=sudo

If you want to go to page 45 of results, you have to visit each and every single page before it by pressing next 44 times...

We should have better widgets for next/previous pagination... and also:

This is related to:

@Rishi-source
Copy link

Rishi-source commented Oct 16, 2024

In my approach for solving this issue

the following improvements to our pagination functionality are recommended:

  1. Direct Page Navigation:
    Implement an input field allowing users to specify and navigate directly to a desired page number.

  2. Enhanced Page Number Display:
    Implement a more comprehensive page number display system, showing a wider range of page numbers (e.g., 1, 2, 3, ...
    10, 11, 12, ... 98, 99, 100) to facilitate easier navigation across the result set.

  3. Alternative Content Loading Methods:
    Consider implementing either infinite scrolling or a "Load More" button as an alternative to traditional pagination.

  4. Adjustable Items Per Page:
    Provide users with the option to increase the number of items displayed per page, thereby reducing the total number of
    pages.

  5. Keyboard Navigation:
    Implement keyboard shortcuts to enable efficient navigation through search results using keyboard inputs.

Please Do let me know if you have some other ideas...

@pombredanne
Copy link
Collaborator Author

and here is some private feedback I received:

I think 2 is the bare minimum, and 4 is obvious.

All other options cater to specific usage patterns, but depend on
scripting.

One more option (also requires scripting) is to filter as you
type (showing only the subset of results containing the string
you've typed). So that if I type "main" or "armhf" I only see those.

@pombredanne
Copy link
Collaborator Author

Based on this starting with 2. using a standard Bulma would be best IMHO. And we can expand later

@Rishi-source
Copy link

Ok I'll Start scripting with the 2 and 4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants