Last modified: 2014-11-10 21:17:19 UTC
With wikitext editing, people work around this by writing long articles in word, or relying on browsers remembering form data if it crashes. Perhaps with local storage we can take periodic snapshots of DM HTML, or even the entire surface state (DM data, IV store, internal list, transaction history etc.) and offer to restore it if the changes went unsaved.
Why not deploy the drafts extension, and add any VE support needed?
(In reply to comment #1) > Why not deploy the drafts extension, and add any VE support needed? [[mw:Extension:Drafts]], for those unfamiliar.
(In reply to comment #1) > Why not deploy the drafts extension, and add any VE support needed? Have commented there explaining.
If local storage is going to be seriously considered, with pages being auto-saved, some issues to consider: How many open VE's can be autosaved? Only saving one VE session makes management very simple, but it is probably sufficient for only a small subset of the editing community. The local storage limit of 5 MB in most user agents is going to be a problem. Also VE needs to intelligently handle the case where the offline storage is not available or the origin has exceeded its limit. The user needs to know when their session isnt being auto-saved due to client side factors. Are these autosaved versions going to persist across browser sessions? If the VE sessions do persist, how will VE determine which VE autosaved versions are no longer needed and can be deleted to allow more VE sessions to be autosaved in the future. Will the user be able to manage which autosaves they no longer need?
*** Bug 52988 has been marked as a duplicate of this bug. ***
See also: Wikitext editor patch for this: https://gerrit.wikimedia.org/r/#/c/5130/
