-
Notifications
You must be signed in to change notification settings - Fork 684
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
Pagination #2067
Comments
When JS is enabled, we should flag it like |
In-work. Currently not taking JS into account. |
- Increases the number of sources in dev data for easier pagination testing - Paginates the list of sources in journalist interface - Fixes the SD logo width for less redrawing during pageload - Handles paginated sorting of starred items - Keeps current pagination upon starring
- Increases the number of sources in dev data for easier pagination testing - Paginates the list of sources in journalist interface - Fixes the SD logo width for less redrawing during pageload - Handles paginated sorting of starred items - Keeps current pagination upon starring
- Increases the number of sources in dev data for easier pagination testing - Paginates the list of sources in journalist interface - Fixes the SD logo width for less redrawing during pageload - Handles paginated sorting of starred items - Keeps current pagination upon starring
- Increases the number of sources in dev data for easier pagination testing - Paginates the list of sources in journalist interface - Fixes the SD logo width for less redrawing during pageload - Handles paginated sorting of starred items - Keeps current pagination upon starring
- Increases the number of sources in dev data for easier pagination testing - Paginates the list of sources in journalist interface - Fixes the SD logo width for less redrawing during pageload - Handles paginated sorting of starred items - Keeps current pagination upon starring
It's worth looking at pagination or similar solutions to address potential timeouts on instances with a large (5k+) number of sources (though obviously the advice to journalists to delete old or unwanted conversations is still sound, the app server should not be seen as a long-term data store). Reopening for now. |
Description
Currently, we have no pagination on results on either the SecureDrop source or journalist interface. For example, this means that if a news organization isn't great about deleting sources then they will have a list of potentially hundreds of sources appear whenever they load the journalist interface. This is bad for usability as it is overwhelming and it increases page load times, which are already slow due to Tor.
User Stories
As a journalist user, I want to see only the N most recent sources on the index so that I'm not overwhelmed with hundreds of sources.
The text was updated successfully, but these errors were encountered: