Community Wishlist Survey 2019/Editing/Improve diff viewer - how it handles line breaks

From Meta, a Wikimedia project coordination wiki

Improve diff viewer - how it handles line breaks


  • I would add to the proposal that split/merged paragraphs should be detected correctly as well. --NaBUru38 (talk) 18:37, 7 November 2018 (UTC)Reply[reply]
  • There was some work done on diffs in the past year or two and I'm not sure it ended up in the right spot. --Izno (talk) 20:28, 7 November 2018 (UTC)Reply[reply]
    • That was WMDE Technical Wishes/Show text changes when moving text chunks, and as they describe in the page there, the related code is intensely complicated. I think this proposal and the new phab task are probably duplicates of phab:T7072. Quiddity (WMF) (talk) 00:00, 8 November 2018 (UTC)Reply[reply]
      • Updated phab tickets section above.. I don't think the proposal is a duplicate, since the ticket you linked is not assigned to anybody, the community tech team can work on it. --Gryllida 00:06, 8 November 2018 (UTC)Reply[reply]
        • Don't worry about things being assigned. If CommTech can take it on, we can change who is assigned. :) --Izno (talk) 23:49, 8 November 2018 (UTC)Reply[reply]
    • Izno: moving paragraphs is better now (see link shared by Quiddity); however, this proposal is about edits which involve splitting a paragraph. --Gryllida 19:53, 17 November 2018 (UTC)Reply[reply]
  • It's probably way beyond the scope of this proposal, but it'd be amazing if the diff view gained the ability to expand context above and below the displayed changes, ala GitHub's diff viewer. (This would be especially valuable for Pending Changes review. Turns out, to properly interpret someone else's changes can often require far more context than the existing changes view displays.) -- FeRDNYC (talk) 10:51, 17 November 2018 (UTC)Reply[reply]
  • What I have faced; the diff viewer is excellent in comparing how the source code get changed; but it is not good to find how the change will appear to the reader after the change is executed. So just not only source code comparison; there should be a separate section/preview pane for comparison of changes in the page's look, changes of texts, rows , columns within tables, changes in pictures, etc. The colour hilight indicator should be present for executed page output comparison too. RIT RAJARSHI (talk) 19:18, 21 November 2018 (UTC)Reply[reply]