[wp-trac] [WordPress Trac] #23497: Revisions Rewrite using JS/Backbone

WordPress Trac noreply at wordpress.org
Sun Mar 10 13:49:29 UTC 2013

#23497: Revisions Rewrite using JS/Backbone
 Reporter:  adamsilverstein            |       Owner:  westi
     Type:  enhancement                |      Status:  reviewing
 Priority:  normal                     |   Milestone:  3.6
Component:  Revisions                  |     Version:  3.5.1
 Severity:  normal                     |  Resolution:
 Keywords:  needs-patch needs-testing  |

Comment (by adamsilverstein):

 i agree, its confusing! my original take on the interface had the
 comparison always be to the previous revision, showing 'whats changed in
 this revision. i think this is what you were expecting to see as well.

 this idea wasn't well accepted in our revisions team meeting and the
 consensus was that the diff view should show the difference between the
 current post data and the viewed revision. i'm not entirely convinced,
 however - i really liked the mode that showed the change in each
 revision... one idea would be to enable a 'compare to previous' feature in
 the single slider handle mode.

 once we get the code a little more polished and clear bugs, i would love
 to see some user testing like the tests of the menu system @lessbloat ran
 a few weeks ago.

 thanks for the feedback and testing, stay tuned here for updates.

 Replying to [comment:63 bpetty]:
 > Replying to [comment:62 adamsilverstein]:
 > >  * from your description though, wouldn't 'four' show in any position?
 note that ''the diff view in single handle mode shows what has changed
 between the current version and the selected revision''. if the current
 version contains the 'four' edit, that will show on the +Added side of the
 diff for every revision comparison. again:  the view shows compare to
 current, not what happened in the revision (i tried it that way, but it
 wasn't liked)
 > How are you supposed to know what content (in the selected revision) you
 are actually restoring then without opening "compare two revisions"? And
 if you do have that open, "restore revision" becomes even more confusing.
 This seems incredibly unhelpful, and definitely confusing if you come from
 the old revisions page or Wikipedia diffs. There's no possible way to see
 what the real changes were in a single revision other than the first
 revision without opening the "compare two revisions" feature, but I always
 thought that was one of the primary use-cases for revisions.
 > MikeHansenMe is right, this is all very confusing UI.
 > You open revisions and start out on a diff from the latest revision to
 the next oldest (MediaWiki provides "prev" links rather than making you
 select both revisions manually for that use case, and I'm guessing they do
 since it's so frequently used), but from there on out, I would *always*
 end up checking "compare two revisions", and painstakingly selecting each
 revision by moving both slider buttons one tick at a time.
 > Anyway, if the way it works now is how it's going to be, you're right
 that it needs to be significantly more apparent - like adding the exact
 revisions (and dates) above each column on Removed/Added.

Ticket URL: <http://core.trac.wordpress.org/ticket/23497#comment:64>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list