You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present, Query log shows paginated data from querylog.json.
At present, the number of lines shown is hard coded, discussed in #1849.
Due to that hard coding and the number of lines shown, the user has to scroll back up to the top of the screen manually (via the means for their OS or device), to continue reading the log top to bottom (unless they don't mind changing their reading direction, but that can be fustrating as all heck for some people).
This increases the work to move through the logs and identify sites that might have slipped the users filters.
Proposed Solution
On the Query Log screen, update the functionality of the previous and next buttons to automatically scroll back to the top of the page; so that the user can continue reading.
Alternatives Considered
None identified.
Additional Information
N/A
The text was updated successfully, but these errors were encountered:
Problem Description
At present, Query log shows paginated data from querylog.json.
At present, the number of lines shown is hard coded, discussed in #1849.
Due to that hard coding and the number of lines shown, the user has to scroll back up to the top of the screen manually (via the means for their OS or device), to continue reading the log top to bottom (unless they don't mind changing their reading direction, but that can be fustrating as all heck for some people).
This increases the work to move through the logs and identify sites that might have slipped the users filters.
Proposed Solution
On the Query Log screen, update the functionality of the previous and next buttons to automatically scroll back to the top of the page; so that the user can continue reading.
Alternatives Considered
None identified.
Additional Information
N/A
The text was updated successfully, but these errors were encountered: