Page MenuHomePhabricator

Saving without leaving visual editor
Closed, DuplicatePublic

Description

In order for visual editor to function smoothly on large articles or in a context of a high editing volume, there are two issues that need to be relieved : performance, as it can take a while to load visual editor on an article of large size, even when it was already loaded once, and edit conflicts, as they are quite regular on heavily edited articles, and it is necessary to use wikitext editor to resolve them, defeating the purpose of having a visual editor. This would be pretty much required in order to achieve a successful implementation on wikis like the English Wikipedia.
The possibility to save an edit without leaving visual editor (meaning there would be two save buttons, one staying on VE and one leaving VE) would help on both counts. Indeed, it can take a while and be a hassle to (1) save the edit (2) load the saved page (3) relaunch visual editor (4) load visual editor. This means users are dissuaded from saving often, which goes against the very common habit of making several small edits rather than a big one, and increases the risk of edit conflicts. If a user could simply (1) save the edit (2) update the visual editor window with the edit and non-conflicting intermediary edits if any, it would be much less of a hassle for the user and the loading time could be optimized by only reloading the updated elements.

Event Timeline

Cenarium raised the priority of this task from to Needs Triage.
Cenarium updated the task description. (Show Details)
Cenarium added a project: VisualEditor.
Cenarium changed Security from none to None.
Cenarium subscribed.

@Cenarium: So the main reason for this request are edit conflicts?

This would be one of the main reasons, it would become much easier to use on heavily edited large articles. But I think it's also important to not disturb the editing habit of making several small edits rather than a big one (because people see this and that which needs fixing, so fix and save, then continue or do something else, change of idea, move on or go back at it, etc). This would make it easier to edit on the fly by reducing load time for repeated edits and not having to relaunch visual editor each time.

This may also be an intermediary step to an "always on" visual editor, as a user preference.