Problem
It is common for one user to edit the same page multiple times in quick succession. This is often because a user made a minor mistake they want to correct, or they decided to make an additional change. (For a real-world example, see my edits on this article.)
We will want to bundle these on the Timeline both for information density and productivity (e.g. it is not always useful to have to view multiple diffs when 1 could suffice.) However, we will need to take into account how some users can hide harassing comments in successive edits. We'll also want to consider how a user could view the byte change and edit summary for each edit.
Use Case 1: Successive innocuous edits
See the edits that Bananas made on this page history. The three diffs combined show this edit which is comprised of this first edit, this second edit and this third edit. Each diff individually is not interesting, but the combined diff is interesting.
This is how this interaction currently looks on the Timeline.
Use Case 2: Hiding a malicious edit in between innocuous edits
See the edits that Apples made on on this page history. The three diffs combined show this innocuous edit but the middle Apples actually made this neutral edit first followed by this malicious edit which is obfuscated by this cover-up edit.
For this case, we will want to provide a way to view each individual edit separately.
This is how this interaction currently looks on the Timeline.
Use Case 3: Successive edits on the timeline, but not in full history.
We'll also need to think about how we treat successive edits when there are edits by other users to that page. For example, on this page there are three users who are editing, but this Timeline only shows two, and it appears that three of Apples' edits are successive, but they are not — there are intermediate edits by Durian.
Either this doesn't matter, and we can address this in the same design solution as the above use cases, or we ignore this type of situation as "non-successive" and they continue to show on the Timeline as individual boxes.
Acceptance criteria
- Only bundle edits that were made within one hour. (TBD final time value)
