[Wikidata-bugs] [Maniphest] [Commented On] T189808: Make action=undo work with multiple slots.

2018-07-12 Thread daniel
daniel added a comment. an "undo without edit" could have all fields' content as or as data stored in the session server-side. No need for even that, all data is already stored on the server side.TASK DETAILhttps://phabricator.wikimedia.org/T189808EMAIL PREFERENCEShttps://phabricator.wikimedia.or

[Wikidata-bugs] [Maniphest] [Commented On] T189808: Make action=undo work with multiple slots.

2018-07-12 Thread Anomie
Anomie added a comment. I note there's no reason the edit form with the undo content would have to actually be editable for any particular field or having the raw content of that field being displayed to the user, as long as the preview and show changes functions work sensibly. In the extreme case,

[Wikidata-bugs] [Maniphest] [Commented On] T189808: Make action=undo work with multiple slots.

2018-07-12 Thread daniel
daniel added a comment. maybe we need undo-without-edit anyway if some slots don't support editing but support undo? Yes. This is already the case for SDC. MediaInfo does not support direct editing.TASK DETAILhttps://phabricator.wikimedia.org/T189808EMAIL PREFERENCEShttps://phabricator.wikimedia.o

[Wikidata-bugs] [Maniphest] [Commented On] T189808: Make action=undo work with multiple slots.

2018-07-12 Thread Tgr
Tgr added a comment. When you are undoing past edits (ie. the "new" end of the undo range is not the current edit), the undo operation creates a content (array of contents, post-MCR) that does not exist on disk. That content needs to be presented to the user and then saved. Currently, EditPage just