[wp-trac] [WordPress Trac] #23497: Revisions Rewrite using JS/Backbone
WordPress Trac
noreply at wordpress.org
Sun Mar 10 18:19:39 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 bpetty):
I understand what @helen was trying to explain, but I think she didn't
realize that the compare page could open the "compare two revisions" mode
with the current version against the revision selected by default (where
applicable), and that's really what she may have meant (maybe you didn't
even have that functionality finished yet at the time?).
If the slider only allows selection of one revision, the changes in just
that revision are what the user wants to see. If the slider allows
selection of two revisions, then we compare the range of changes. As far
as the actual UI control logic, that seems entirely clear.
What you have in trunk right now is two different modes where the
functionality of one of them (the single revision selection) is already
covered by the second mode, and so now it doesn't really provide any
advantage over the "compare two revisions" mode. And in the process of
doing this, it's now also not possible to easily browse single revision
changes. The two modes are there to complement each other with
functionality the other mode doesn't provide, right? Otherwise there's not
much point in even having the second mode.
@helen, it would be helpful to see the report of the actual survey
mentioned, it might help give us some insight into what you mean.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/23497#comment:67>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list