Author: ayg
Description:
Mockup of proposed interface
Currently we have two options, undo and rollback, that have nearly identical functionality but different names and slightly different functionality and different availability. The difference between them is not made clear to new users. The code paths are also entirely different, which results in unnecessary differences in functionality. Differences that I know of are
- Rollback works immediately, no intermediate confirmation page with diff.
- Rollback can be restricted and is by default.
- Rollback does not work on old edits.
- Rollback works on all consecutive edits by a user, always, whereas undo normally works on exactly one revision and can work on an arbitrary stretch of revisions if given the proper URL parameters.
- They're called something different.
(1) is the reason for (2), and those two should be the only difference between the two sets of functionality. (3) and (4) should be adapted to give rollback the same (superior) functionality as undo. (5) should be eliminated, preferably in favor of the more intuitive term "undo". Rollback could be called "quick undo". In the course of adding the flexibility of undo, it makes the most sense to adopt its URL scheme for rollback, perhaps with parameters such as quickundo{,after} instead of undo{,after}, or with an additional &quick=1 parameter.
I've attached a mockup for the proposed interface.
Version: unspecified
Severity: enhancement
Attached: