38

Now we have a nice side-by-side diff in the 'suggested edits' review pages, and as an option in edit history, could something similar be made available as an option when editing a post?

It wouldn't need to be interactive - a button to get the side-by-side diff of the current state of your edit, versus the original would do. This would be useful when shuffling lots of whitespace around - a final check that you haven't broken some embedded code.

A workaround at the moment is to submit the edit, then check the side-by-side view in the edit history.

  • 2
  • 8
    This will also help to create the edit summary when doing longer edits. – Paŭlo Ebermann Sep 12 '11 at 22:49
  • I would love this... especially since the workaround only works for >2k users. – Jonas Heidelberg Oct 8 '11 at 18:00
  • ... I have to correct myself: on my own activity page, there is a link to my suggested edit in diff format. – Jonas Heidelberg Oct 10 '11 at 0:09
  • 3
    Commenting today because I just ran into this problem. I'd like to see what I've changed before I submit the edit, to make sure that I didn't change the meaning of any of their sentences. – Riking Mar 25 '13 at 15:44
  • 1
    Since i recently learned, that stuff went missing in my edits while reformatting post or questions, i'd also like that very much to reconfirm that all the data is still there. – scones Apr 6 '13 at 7:23
  • 5
    This is not a duplicate of 72645 - that refers to viewing the effect of an edit after the fact, whereas this request is for a side-by-side whilst editing. I thought that was clear in the question, apparently not. – martin clayton Apr 10 '15 at 6:42
  • Agreed, this is about seeing a diff before submitting the change. The other post was a feature request about how diffs are displayed after submitting. Voted to reopen. – Martijn Pieters Apr 10 '15 at 7:25
  • The workaround is nice but doesn't help for edit suggestions, where a good description of the edit is especially important. – guntbert Feb 21 '16 at 12:27
1

This is one of the features I find missing most often.

There are several reasons I think this feature would make a big difference:

The biggest:

  • At the end of an extensive edit I want to make sure I captured the OP's original meaning and intent. While I can open the original post in a new tab, and compare the original with the edited version, that method is far from satisfactory. It is not easy to see the changes, and it is easy to overlook things. If, on the other hand, I could see the diffs side by side, I could easily and accurately check my edits against the author's original meaning.

  • Sometimes when moving large pieces of text around, it is easy to drop some of it. Occasionally I have nearly deleted parts of a post unknowingly. Being able to check the diffs would make it super easy to recognise and correct this.

Some other good reasons:

  • As a less than 2k rep user, I want to be able to see what the reviewer sees, making it easy to see if my edit would appear satisfactory to the reviewer.

  • As Paŭlo Ebermann metioned, seeing the diffs would make it easier to write the edit description for long edits.

  • I want to be able to see how much the post has changed, making it easy for me to tell if an edit is a worthwhile or not. Sometimes I start editing a post, only to eventually decide that I can't improve the post that much without essentially starting from scratch. If I could see the difference early on, though, I might save some time.

  • It would allow me to check my writing style against the OP's, making sure that they are not too different.

These are just a few reasons to implement this, and I am sure there are many more. I believe this feature would help me edit better, and I wish that the dev team would revisit this .

If you know of any other good reasons, please let me know in the comments.

1

My current workaround for lack of this feature results in the following workflow:

  1. Do the edit, make sure it looks as you intended, not submitting yet
  2. Ctrl+A, copy & paste into a text editor, save as file like new.md
  3. Discard the edit by clicking the button in the web UI
  4. Start editing again, save the original text into another file, like old.md
  5. Use your favorite local diff viewer (I use kdiff3) to check the diffs, fix new version as necessary
  6. Copy & paste the new version from new.md to the edit box in the web UI
  7. Submit the edit.

A more forward-looking approach would be to save old.md before starting to edit, of course. Then you won't need to discard the edit to get original text. Or use other ways of getting original text after you've changed that in the edit box – e.g. holding Ctrl+Z to go back via repeated undoings, or navigating to a URL like https://meta.stackexchange.com/posts/<YourPostId>/revisions, where <YourPostId> is the Id of the post you can find after /a/ part in the share link.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .