Problem: Sometimes one user makes many edits after each other. As somebody who controls the quality of the article, I want to see all changes made at once, and not seperated in edits (which makes it harder to understand the edits as a whole). It is possible to see the revisions authors at a glance in the history view. In the revision slider, this is more complicated
Solution:
- Next to the user name in the info tool tip, add a bubble (as shown in the mock).
- When users hover over that bubble, the user name row is circled, and all revisions of that user are highlighted. Once the hovering ends, the highlighting ends.
- When users click on the bubble, the user name row is circled, and all revisions of that user are highlighted. The highlighting stays, until the bubble is clicked again, or until another user name was selected.
- There is always just one active filter. E.g. if currently all edits by a certain user are highlighted, and then I select the bubble next to the blanked tag, the filter for the specific user is lost, and only edits with the blanked tag are highlighted
- Highlighted revisions through hovering does not remove a currently active filter. E.g. if currently all edits user A are highlighted, and then I hover over the bubble of user B, I only see revisions of user B and not the edits of user A. However, when I don't hover over the bubble of user B, the filter for user A is reinstated again
- The filter behavior when something is selected or hovered over always works as described above, no matter if the competing filters are tag or user name filters.
Design details:
circle color changes: normal:#E3E3E3, selected: #CCC, border: 1px black, 30% opacity.
border around the row when selected: #E0E0E0
The corresponding edit-bars in the diagram also change color: 10% darker, border black, 30% opacity.
Mock
Notes
Although the mock shows bubbles both for user names and tags, this ticket is for user names only. The tag filtering is handled in T203581. At the end, users should have the same experience in both cases, though.
