I've been having system problems lately, and crashing a lot. Before using VisualEditor, Chromium and Firefox saved my edits when restoring sessions, as long as I am using a persistent login. When using VisualEditor, they are unable to do this. Some type of recovery of in-process edits would be a really nice feature. I think at least for the time being, the lack of this feature is going to prevent me from using it anymore, maybe forever.
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
VE has an autosave feature that keeps all your changes stored in sessionStorage. If your browser crashes and you recover the same tabs it should restore your edits. You should be able to simulate a browser crash from your OS's task manager, or by going to chrome://crash.
If you can reproduce making edits -> crashing the browser -> not having those edits recovered on reloading the same tabs, then please update with more instructions.
Comment Actions
To clarify, is this about browser (or browser tab) crashing, or about your whole computer crashing (bluescreen, power loss)? I think in the second case we'll fail to recover the edits currently.
Comment Actions
I think in the second case we'll fail to recover the edits currently.
Probably not if you have your browser set to restore your tabs.
Comment Actions
Losing in-process edits (or any kind of work for that matter!) is frustrating and something we're actively thinking about [1] – thank you for raising this, @jamespharvey20.
As to the particular issue this task is responding to, like @Esanders mentioned:
...and @matmarex mentioned:
...sharing the steps that produced this issue would go a long way in helping us reproduce the issue you're experiencing en route to a potential solve.
- Exploring autoSave: We are exploring autoSave, and more specifically, our current implementation of it here (in case you'd like to follow the conversation in real-time): T218663: Consider switching from sessionStorage to localStorage for autosave
Comment Actions
Unfortunately closing this Phabricator task as no further information has been provided.
@jamespharvey20: After you have provided the information asked for and if this still happens, please set the status of this task back to "Open" via the Add Action... → Change Status dropdown. Thanks!