mirror of
https://gerrit.wikimedia.org/r/mediawiki/extensions/VisualEditor
synced 2024-11-24 22:35:41 +00:00
74cb83d2f8
When we moved to mw.Api, edit conflict errors stopped going via onSave and started going to onSaveError instead. So the case to check for them in onSave would not have worked - instead, they would go through onSaveError and get picked up by our unknown error code, which just picks out error.info and shows it, instead of showing our edit conflict screen. Also return in a couple of other error cases where we probably should've been (but not necessarily must've been... that didn't necessarily show to the user if another error emit already caused saveDeferred to be rejected) Change-Id: Iae7a66a8aa96ee777e9fa780005feeb429129d5f |
||
---|---|---|
.jsduck | ||
bin | ||
build/tasks | ||
lib | ||
modules | ||
.csslintrc | ||
.gitignore | ||
.gitmodules | ||
.gitreview | ||
.jscsrc | ||
.jshintignore | ||
.jshintrc | ||
.mailmap | ||
.rubocop.yml | ||
.rubocop_todo.yml | ||
ApiVisualEditor.php | ||
ApiVisualEditorEdit.php | ||
AUTHORS.txt | ||
betafeatures-icon-VisualEditor-ltr.svg | ||
betafeatures-icon-VisualEditor-rtl.svg | ||
composer.json | ||
CONTRIBUTING.md | ||
extension.json | ||
Gemfile | ||
Gemfile.lock | ||
Gruntfile.js | ||
jsduck.json | ||
LICENSE.txt | ||
package.json | ||
README.md | ||
VisualEditor.hooks.php | ||
VisualEditor.php | ||
VisualEditorDataModule.php | ||
VisualEditorViewPageTargetInitModule.php |
VisualEditor
VisualEditor provides a visual editor for wiki pages. It is written in JavaScript and runs in a web browser.
It uses the Parsoid parser to convert wikitext documents to annotated HTML which the VisualEditor is able to load, modify and emit back to Parsoid at which point it is converted back into wikitext.
For more information about these projects, check out the VisualEditor and Parsoid pages on mediawiki.
Developing and installing
For information on installing VisualEditor on a local wiki, please see https://www.mediawiki.org/wiki/Extension:VisualEditor
For information about running tests and contributing code to VisualEditor, see CONTRIBUTING.md. Patch submissions are reviewed and managed with Gerrit. There is also API documentation available for the VisualEditor.