Help talk:Paragraph-based Edit Conflict Interface

Jump to navigation Jump to search

About this board

Feedback and discussion page for the Paragraph-based Edit Conflict Interface.

Update: We completely revised the interface for this feature based on user feedback and user test.

Report a new bug in Phabricator

You can post in any language here, preferably English or German.

Liz (talkcontribs)

For some reason, this "tool" posts my comments duplicate times, as if I have an edit conflict with myself. I then have to go back and remove the excess comments from the page. This has happened more often than not with this tool. When I have a chance, I'll try to figure out how to disable it.

Thiemo Kreuz (WMDE) (talkcontribs)

Thank you for the report. Unfortunately, I'm not sure what kind of response you expect? Are you able to post some example links where this happened? That would help a lot investigating this issue further. So far it sounds like a long known issue with the edit conflict detection algorithm in MediaWiki core, which is what TwoColConflict depends on. See for example phab:T28821, phab:T36423, phab:T59264, or phab:T222805. TwoColConflict is essentially just an interface on top of that.

Liz (talkcontribs)

Well, when the Beta feature pops up, I get a message to come here to offer feedback so that's what I did. I don't know if I have expectations, I just followed the suggestion to come here and post.

You can see one example of this if you look at my contributions and look at the posting to WP:ANI at 21:03, November 5, 2021. It posts twice in the same moment and the next edit I delete the duplicate entry.

Thiemo Kreuz (WMDE) (talkcontribs)

I would love to do something about this. Let's see. There are two edits, the first at 04:03:14 UTC, the second 27 second later. That's not exactly the same moment. Furthermore, the second edit is marked as a revert. Why is that?

Reply to "Argh!"

Problem with paragraph spacing

Summary by Thiemo Kreuz (WMDE)
SnowFire (talkcontribs)


I had this gadget enabled for quite some time, but after various issues have finally bitten the bullet and disabled it. The last straw was one particular issue that I hope is just a bug: a user on English Wikipedia had gone through and inexplicably removed most line breaks. They'd made several other changes I didn't want to revert, so I couldn't just revert the entire edit, so I bothered to go back and add in all the removed line breaks by hand. This user by then had made yet another edit, so the edit conflict window came up. Despite clicking on "my side" for each option, it didn't matter - all those line breaks I re-added were thrown away. That can't have been intended behavior. Hopefully this suffices as reproduction steps, but is this fixable? I would link the edit in question but get an "abusefilter warning linkspam" when I do so...

Thiemo Kreuz (WMDE) (talkcontribs)

Thanks a lot for the report! This is indeed not how the interface is meant to behave. I found the edits (1, 2, 3) and was able to reproduce and fix the issue locally. It's tracked at phab:T284994 now.

Deployment as a default feature

Trizek (talkcontribs)


Is there any plan to deploy this feature to more wikis?

Can a single wiki ask to have it deployed as default?


Johanna Strodt (WMDE) (talkcontribs)

Hi Trizek, thanks a lot for your question. I don't have an answer yet, we need to discuss this in our team first. I'll let you know once we know. :)



Reply to "Deployment as a default feature"
Skalman (talkcontribs)

In the old version, the following scenario works as expected:

  1. Edit a page
  2. Attempt to save, resulting in an edit conflict
  3. Edit the original text
  4. Click "Show Changes", to view the new diff

Step 4 doesn't seem to be available any longer. I usually like to use the diff before saving something, especially in complex situations like handling an edit conflict.

Overall, it seems like a great addition to the editing workflow!

Reply to "Can't see updated diff"

Question about using this for another purpose

Krzysiek 123456789 (talkcontribs)

Hello, I have a question is it possible to somehow artificially cause an "edit conflict" between two selected versions of a page? My question is motivated by the fact that this would be very useful overridden to work with flagged versions. It would allow, for example, to compare the differences between flagged and non-flagged versions by paragraphs. This would be very because you could select individual changes that should be withdrawn, and all the rest of the positive to leave. Best regards.

Thiemo Kreuz (WMDE) (talkcontribs)

I'm not sure if I got the question. But it's easily possible to create diffs between any version.

  • In the page's history, click the tiny radio buttons next to the two versions you want to compare and click "Compare selected versions".
  • Enter e.g. Special:Diff/4513235/4694855 in your browser's URL bar with the two revision numbers you want to compare. They can even be from two different pages.

Manually triggering the TwoColConflict interface the same way is currently not possible.

Krzysiek 123456789 (talkcontribs)

You understood the question well, I know perfectly well that you can do diff, but it does not allow you to select by paragraphs the changes to leave. You can only compare versions and possibly rollback everything. Is there somewhere e.g. in Phabricator or on Github where I can ask developers about this, because they must have some way to execute this for testing.

Thiemo Kreuz (WMDE) (talkcontribs)

The extension was developed by my team, but there is currently no budget to develop it further. What you ask for sounds like "partial undo". While I understand the similarities, I think this would need to be a separate feature. Phabricator is the place to discuss feature requests.

Krzysiek 123456789 (talkcontribs)

I know this would have to be implemented separately, but I was thinking of using your extension (since it already exists and is installed on the Wiki I most frequently contribute to) to present this to others and convince them that it's cool.

Reply to "Question about using this for another purpose"
Summary by Thiemo Kreuz (WMDE)

Probably means the Meta wiki. (talkcontribs)

Hi ineed to know what is Meta I New in this app

Thiemo Kreuz (WMDE) (talkcontribs)
Enterprisey (talkcontribs)

Great tool; well done to everyone who worked on this, for making something really cool and solving a tough problem.

Czeva (talkcontribs)

Hi, just want to say thank you for the tool, which I have just been confronted with for the first time and which I find really helpful. Good job :-)

del tag and white-space: pre-wrap

Summary by Thiemo Kreuz (WMDE)


DonRumata (talkcontribs)

Please add rule .diffchange-inline { white-space: break-spaces; } because Google Chrome incorrect displays diffs with deleted trailing spaces, which tagged inside .diff-deletedline. See Diff Test in Google Chrome. ~~~~

Thiemo Kreuz (WMDE) (talkcontribs)

Thanks for the report, Unfortunately this is unrelated to the two-column conflict-resolution interface. However, thanks to the super helpful example it was easy to create a patch, see gerrit:651181.

DonRumata (talkcontribs)

You accidentally left the old rule white-space: pre-wrap;.

Thiemo Kreuz (WMDE) (talkcontribs)

That's called a fallback for browsers that don't understand the value further down. MediaWiki still needs to support Internet Explorer 11, that's why I did it like this.

Edit conflicts (with myself)

Nick Moyes (talkcontribs)

Quite frequently I post a reply and find an Edit Conflict alert, but then discover that my post was published and that the edit conflict notification is actually with myself. It's as if I've double-clicked 'Publish', and my second (blank) edit is trying to overwrite my original response.

I find this quite annoying, though I do generally like the interface as I edit at a very active Forum (the English Wikipedia Teahouse). I am using Winndows 10 Home 64 bit, on Chrome browser Version 86.0.4240.198

My one suggested improvement is to provide a 'Click to copy contents' button so I can quickly select my reply text and ensure I don't completely lose it if things don't work.

Michael Schönitzer (WMDE) (talkcontribs)

Hi, that should not happen. Most likely it's not due to the Paragraph-based Edit Conflict Interface but due to some other changes on the software. We know that a team of the Foundation currently works on something very related. If this happens again, could you please send us an screenshot and the link to the edit?

Nick Moyes (talkcontribs)

Yes - will do that.

Vachovec1 (talkcontribs)

I can confirm this exact behavior. At least one other editor on cs-wiki also encountered this : . It seems to happen occasionally on discussion pages. The last time it happened for me today here:,_Jando%C5%A1,_%C5%A0%C3%ADma,_Pechmann&action=history . First version of the page (13:31 CET) is the result of clicking on "publish" button. At the same time, the editation conflict interface was inicialized, reporting editation conflict, presumably with myself. The second version of the page (13:32 CET) is the result of "resolving" that editation conflict.

Editing in wikitext editor 2010, Chrome browser, desktop. Other editor on our wiki reports this behavior from Chrome browser on desktop as well, but also from Chrome on Android, classic (not mobile) view.

Nick Moyes (talkcontribs)

I have received some responses from editors at the en-wiki Teahouse (see here) who have also experienced edit conflicts with themselves. I have also captured a screenshot, as requested. See here.

Having tried saving a few edits with very rapid double-clicks of my mouse, I am now starting to wonder whether this might actually be more of an issue caused by over-responsiveness of the blue 'Publish' button which ought not to be able to act on a second mouseclick (or tap) immediately afterwards at all. I tried this intentional rapid double-click on my own talk page, which did cause an edit conflict report . Resolving the conflict only modified the timestamp (rather than adding in a duplicate copy of what I'd posted), but the time wasted in wondering why one has got an edit conflict is probably quite significant - and especially so on busy, talk pages and help fora.

Maybe the folks behind this tool can push to get that over-responsiveness of the mediawiki software Publish button addressed if, as now seems probable, the fault actually lies elsewhere?

Reply to "Edit conflicts (with myself)"