Last modified: 2013-07-04 16:44:05 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T52753, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50753 - VisualEditor: edit conflict handling
VisualEditor: edit conflict handling
Status: RESOLVED INVALID
Product: VisualEditor
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: James Forrester
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-04 16:09 UTC by Oliver Keyes
Modified: 2013-07-04 16:44 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Oliver Keyes 2013-07-04 16:09:07 UTC
In the case of an edit conflict, the structure of the VE means that the common workaround (taking discrete wikimarkup changes, copying them, opening the newly revised article, pasting them in) doesn't work. What's the plan to handle ECs in the VE?
Comment 1 James Forrester 2013-07-04 16:44:05 UTC
(In reply to comment #0)
> In the case of an edit conflict, the structure of the VE means that the
> common workaround (taking discrete wikimarkup changes, copying them, opening
> the newly revised article, pasting them in) doesn't work. What's the plan to
> handle ECs in the VE?

What do you mean, 'plan'? Have you not encountered one yet? It works very simply: on saving, you get a message like "Sorry, the page couldn't be saved because of an edit conflict. Click here to resolve manually" and then takes you to the normal wikitext edit conflict page, with the wikitext of your new version below and the new current version above, as always.

It's been this way for months. There are enough bugs filed without adding ones. :-)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links