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

WordPress Trac noreply at wordpress.org
Sun Mar 10 16:50:27 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):

 Replying to [comment:65 nacin]:
 > Replying to [comment:64 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.
 >
 > Huh? This makes very little sense. Single-handle scrubber mode should
 show what changed in that particular revision. Comparing to current is
 very unexpected behavior. If you wanted to compare to current, you have
 the two-handle scrubber.

 ok, glad you agree with the concept of the single handle slider showing
 ''whats changed in each revision compared to the previous revision''
 instead of ''whats changed between each revision and the current
 version''. thats the way i thought it should work and thats the way it was
 originally coded in my backbone code, but in our meeting
 [https://irclogs.wordpress.org/chanlog.php?channel=wordpress-
 dev&day=2013-02-18&sort=asc#m558028 IRC chat], @helen felt that was
 confusing to the end user and the consensus seemed to be the comparison
 should be to the current version...

 so, should i just reverse that decision and go back to showing each
 revision's changes, or should we offer an option? will bring up at
 tomorrows office hours, appreciate any feedback.

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


More information about the wp-trac mailing list