[wp-trac] [WordPress Trac] #23497: Revisions Rewrite using JS/Backbone
WordPress Trac
noreply at wordpress.org
Sun Mar 10 22:36:34 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):
Looking through the responses on this survey, it's actually interesting to
note that a large portion of users (about 25%) looking at revisions are
expecting to be able to compare the changes in an autosave from the
published version to see what was saved. This actually makes a lot of
sense. If someone were to restore an autosave, something interrupted them,
and now they have no idea what changes were saved in the autosave, and
which weren't. Some responses also indicated that some users thought that
revisions could help them compare the changes they've made right there in
the editor, regardless of autosave or published revisions (much like how
MediaWiki has a "show changes" option from their editor).
Is there really any reason autosave revisions shouldn't also be available
to compare with regular revisions (because they aren't right now)? They
are a revision with changes, even if they aren't published.
If they were included, the UI would certainly have to be clear (with some
kind of indicators in the slider, and in the diffs) about which revision
is the current published revision, but otherwise, I don't see any reason
why they shouldn't be available for comparison.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/23497#comment:71>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list