Page MenuHomePhabricator

Add 'Oldest first' option to the 'Number of changes selector'
Open, Needs TriagePublic

Description

The Number of Changes Selector enables users to select how many changes they wish to see in Recent Changes results. In addition to the functions described in T162786, the tool will also include an option for 'Oldest first' mode.

  • The menu also includes the following "Sorting" options, with associated radio buttons: "Newest first", "Oldest first"
  • Clicking "Oldest first" causes the following to happen:
    • Results are re-sorted, so that the result at the top of the list comes from 30 x 24 hours ago, and all the other changes are displayed in chronological order from that point.
    • The top-level label on the Number of Changes Selector changes from "Show last x changes" to "Show oldest x changes."
  • When results are in "Oldest first" mode:
    • The "View newest changes" link is not displayed, either on the first, main page or the "last" page, (which now has the newest results).
    • Live Updates is unavailable and the button is grayed out.
    • The "Newer X" and "Older X" pagination buttons continue to do what their names suggest: however, this means the direction of navigation they facilitate is reversed. E.g., "Newer X" takes users "back" away from the main RC Page and toward what's now the bottom of the queue (where results are newest), while the "Older X" pagination button takes users toward the top of the queue and the main RC Page (where results are oldest).
      • On the very "last" page of results, where the newest results are, the "Newer" button is grayed out—and it stays grayed out. I.e., we do not offer the user the option to keep paging in to the future as newer results become available in Oldest First mode.

Reflecting the settings in the drop-down label
In order to capture the current status, the drop-down label will reflect the current settings. For this particular case, selecting "oldest first" will be reflected by replacing "Show last X changes" by "Show oldest X changes". The diagram below shows how the initial message is adapted to the different changes in size, sort order and grouping (check T168513 for more on grouping). Not all combinations are illustrated (e.g., First 500 changes by page") but the examples shown should be enough to describe how the messages should be built.

Layout guidelines

Event Timeline

Restricted Application removed a project: Patch-For-Review. · View Herald TranscriptAug 2 2017, 2:18 AM
jmatazzoni renamed this task from Add to Add 'Oldest first' option to the 'Number of changes selector'.Aug 2 2017, 2:20 AM
jmatazzoni updated the task description. (Show Details)

@Pginer-WMF How are users meant to know when they are in Oldest First mode (except by looking at the dates, of course). Particularly because some functions, like Live Updates, will be grayed out. I feel like you devised some way to indicate that at the top level—by changing the language of the readout perhaps? But I don't remember what ticket those designs were in.

@Pginer-WMF How are users meant to know when they are in Oldest First mode (except by looking at the dates, of course). Particularly because some functions, like Live Updates, will be grayed out. I feel like you devised some way to indicate that at the top level—by changing the language of the readout perhaps? But I don't remember what ticket those designs were in.

This was described in T168513. The basic idea is to surface the selection in the button label as indicated by this diagram:

jmatazzoni added a comment.EditedAug 2 2017, 6:56 PM

@Pginer-WMF Thanks. I knew it was someplace. "...first 50 changes" is ambiguous, I think. It could mean "the first" meaning those that we will show you first (followed by the next and the next...). I suggest we change that to "Show oldest 50 changes"? I went ahead and put that in the spec. Let me know if you have an issue.

jmatazzoni removed the point value for this task.

@Pginer-WMF Thanks. I knew it was someplace. "...first 50 changes" is ambiguous, I think. It could mean "the first" meaning those that we will show you first (followed by the next and the next...). I suggest we change that to "Show oldest 50 changes"? I went ahead and put that in the spec. Let me know if you have an issue.

Makes sense. I created a new mockup and will update the affected tickets next.

Pginer-WMF updated the task description. (Show Details)Aug 3 2017, 9:49 AM
Restricted Application added a project: Growth-Team. · View Herald TranscriptFeb 26 2019, 8:42 AM