Change Details

As part of extending the capabilities of the new filters for edit review (T162675), we may want to provide easier ways to move through the list of contributions. Pagination controls can help users to move forward and back though the results for a more exhaustive review of recent changes or backlogs. Depending on the technical characteristics of the specific page (Recent Changes, Watchlist, etc.) the pagination approach may or may not be applicable in each case. For those cases where pagination can be applied, the proposed approach is described below: |{F7663016}|{F7663018}| - Previous and next controls are provided to navigate to another set of results. -- The page size will be reflected on the controls (and will be updated if the user changes it). -- In order to facilitate operation, the controls will be either (a) made sticky to remain accessible at the top of the viewport (more details on this below), or (b) be replicated at the bottom of the list. - Where pagination controls are available, the advanced filtering options will be provided through the "Advanced settings" button. In this way, less frequently used functions don't distract from the navigation controls. The mockup below illustrate how navigation controls can be provided as part of a sticky header along other entry points to quickly access filtering functionality: {F7663139} - The search button provides a quick access to jump into the filters on top. It displays in the label the name of the user stored quick link if any, or some of the filter names as a reference. - Access to quick links can be provided to facilitate the switching between review activities.

Pagination controls enable users to move forward and back though the Recent Changes results a in order to move backwards and in time. These controls enable users to "walk" back through results to survey changes in a continuous stream, or to jump ahead or back to particular locations in the results queue. ==The 'Newer X' and 'Older X' buttons - "Newer X" and "Older X" buttons are provided to navigate through the Recent Changes queue one page at a time. - When users click these buttons, they will move either forward or backwards through the results queue by the number of results currently selected in the "Number of Results Selector" (T162786) - The labels of the Newer and Older buttons will reflect the the number of results currently selected in the "Number of Results Selector" (T162786). E.g., if the Selector is set to 100, the Older button label will read: Older 100 > - As the user pages backwards or forwards in the queue, the Search tools remain visible and available at page top, showing all the current search terms. - When the user first loads a page of new results, the "Newer" button is grayed out. It changes back to the black, active state as soon as the system determines that the first new result matching the current query has entered the queue. (This test needs to be made for the "View Newest Changes" function anyway T163426. Thus these tools will both update at the same time.) - If the user presses Newer at the moment the button changes color, the one available result will display (meaning that this is really the "up to 100" button.) - The Recent Changes queue drops older changes when they are > 30 x 24-hours old. If the user loads the very last, oldest available page of results, the "Older" button grays to show that the limit has been reached. - If a user, having loaded that very last page, a) sits on the page for a time and then b) presses "Newer," it's likely that the temporally continuous results the user might have expected will no longer be available (because they are now > than 30 x 24-hours old). In this eventuality, the system will simply load a page full of X results that are as close as it can get to what the user requested (i.e., a page of results that are discontinuous from the former "last" page). - !!@Pginer-WMF, I think we should put pagination navigation at the bottom of pages as well, since getting to the bottom and then wanting to go to the next page is a common pattern. Roan says we can't have fancy controls, like the Google bottom navigation, that let you skip 4,5,6 etc. pages ahead or back. So, we're limited to one page at at time plus "oldest" and "newest" links. Do you want to use the nav we already have, e.g, at the bottom of History page? Or would you like to repeat the Older and Newer buttons and add to them Oldest and Newest links... What do you think?!! =='Oldest first' mode When results are in "Oldest first" mode (T162786): - The "Newer X" and "Older X" pagination buttons continue to do what their names suggest. However, this means the perceived "direction" of navigation they facilitate is reversed. I.e., "Newer" takes users "back" away from the RC Page and toward what's now the bottom of the queue (where results are newest), while the "Older" takes users toward the top of the queue and the main RC Page (where results are oldest). - If a user in Oldest First mode gets to the "last" page in the queue (i.e., the one with the newest results), the "Newer" button is grayed out—and it stays grayed out. I.e., it does not offer the option to load newer results to the //bottom// of the queue as they become available. !!@Pginer-WMF, please provide relevant mockups with updated "Older" and "Newer" language.!!

As part of extending the capabilities of the new filters for edit review (T162675), we may want to provide easier ways to move through the list of contributions. Pagination controls can help users to movePagination controls enable users to move forward and back though the results for a more exhaustive review of recent changes or backlogs. Depending on the technical characteristics of the specific page (Recent Changes, Watchlist, etc.) the pagination approach may or may not be applicable in each casRecent Changes results a in order to move backwards and in time. For those cases where pagination can be appliedThese controls enable users to "walk" back through results to survey changes in a continuous stream, the proposed approach is described below: |{F7663016}|{F7663018}| - Previous and next controls are provided to navigate to another set of results.or to jump ahead or back to particular locations in the results queue. ==The 'Newer X' and 'Older X' buttons -- The page size will be reflected on the controls (and will be updated if the user changes it)- "Newer X" and "Older X" buttons are provided to navigate through the Recent Changes queue one page at a time. -- In order to facilitate operation, the controls will be either (a) made sticky to remain accessible at the top of the viewport (more details on this below) When users click these buttons, or (b) be replicated at the bottom of the list.they will move either forward or backwards through the results queue by the number of results currently selected in the "Number of Results Selector" (T162786) - Where pagination controls are availableThe labels of the Newer and Older buttons will reflect the the number of results currently selected in the "Number of Results Selector" (T162786). E.g., the advanced filtering options will be provided through the "Advanced settings" button.if the Selector is set to 100, In this waythe Older button label will read: Older 100 > - As the user pages backwards or forwards in the queue, less frequently used functions don't distract from the navigation controls. The mockup below illustrate how navigation controls can be provided as part of a sticky header along other entry points to quickly access filtering functionality:the Search tools remain visible and available at page top, showing all the current search terms. {F7663139}- When the user first loads a page of new results, the "Newer" button is grayed out. It changes back to the black, active state as soon as the system determines that the first new result matching the current query has entered the queue. (This test needs to be made for the "View Newest Changes" function anyway T163426. Thus these tools will both update at the same time.) - If the user presses Newer at the moment the button changes color, the one available result will display (meaning that this is really the "up to 100" button.) - The Recent Changes queue drops older changes when they are > 30 x 24-hours old. If the user loads the very last, oldest available page of results, the "Older" button grays to show that the limit has been reached. - If a user, having loaded that very last page, a) sits on the page for a time and then b) presses "Newer," it's likely that the temporally continuous results the user might have expected will no longer be available (because they are now > than 30 x 24-hours old). In this eventuality, the system will simply load a page full of X results that are as close as it can get to what the user requested (i.e., a page of results that are discontinuous from the former "last" page). - !!@Pginer-WMF, I think we should put pagination navigation at the bottom of pages as well, since getting to the bottom and then wanting to go to the next page is a common pattern. Roan says we can't have fancy controls, like the Google bottom navigation, that let you skip 4,5,6 etc. pages ahead or back. So, we're limited to one page at at time plus "oldest" and "newest" links. Do you want to use the nav we already have, e.g, at the bottom of History page? Or would you like to repeat the Older and Newer buttons and add to them Oldest and Newest links... What do you think?!! =='Oldest first' mode - The search button provides a quick access to jump into the filters on top. It displays in the label the name of the user stored quick link if any, or some of the filter names as a reference.When results are in "Oldest first" mode (T162786): - Access to quick links can be provided to facilitate the switching between review activitiesThe "Newer X" and "Older X" pagination buttons continue to do what their names suggest. However, this means the perceived "direction" of navigation they facilitate is reversed. I.e., "Newer" takes users "back" away from the RC Page and toward what's now the bottom of the queue (where results are newest), while the "Older" takes users toward the top of the queue and the main RC Page (where results are oldest). - If a user in Oldest First mode gets to the "last" page in the queue (i.e., the one with the newest results), the "Newer" button is grayed out—and it stays grayed out. I.e., it does not offer the option to load newer results to the //bottom// of the queue as they become available. !!@Pginer-WMF, please provide relevant mockups with updated "Older" and "Newer" language.!!