Make edits auto-recoverable if the editor's network crashes
Problem: An WP edit is lost when the editor's network goes down. Saving in-progress work is a feature in VisualEditor and the 2017 wikitext editor, but not the older wikitext editor
Who would benefit: Users of classic wikitext editor who develop a post off-line.
Proposed solution: Like GMail, routinely autosave an editor's in-progress work
More comments: Again, like GMail, create periodic saved-data (a snapshot of work to date) that can easily take over from the lost data of whatever type (message, article text, etc.)
Is the feature enabled on all wikis? I've only noticed it on en.wiki. Would be cool to have a save button, or to know when a save has been made. Many editors publish (way too) often in fear of losing their changes. Ponor (talk) 03:05, 22 November 2020 (UTC)[reply]
1) I am curious, in which cases/situations the VisualEditor and the 2017 wiki text editor are able to restore the lost sessions? If I close a browser tab with non-saved edits, and restore, my edits are gone. Unlike by the Reply tool (Discussion Tools). What is the difference?
Motivation for my questions: request for an auto-save (restore) feature on the local wishlist, and I am not sure how and where to address it here: does it need new development, or only implementation of existing features. Samat (talk) 17:52, 29 November 2020 (UTC)[reply]
Edits are stored in sessionStorage, which means they should be recovered if you restore the same tab, but not if you reopen the page in a new tab. In order to support that we would need to use localStorage, but that comes with issues around storage limits. ESanders (WMF) (talk) 13:55, 24 December 2020 (UTC)[reply]
Have been having this problem for a while also. Yes, my edits are stored locally in some cases but in some others it is still able to be lost. The most recent that I remember was some months ago when a user starts editing a page after I started editing it and then they published it before I published mine. My edit was gone completely and I need to start it all over. Often happens by vandals or bots on Wikipedia. It has also happened before when my Internet went down so my edit was not published and when I went back in my browser, it showed the "can't connect" page so my cached edit was lost. RXerself (talk) 00:31, 9 December 2020 (UTC)[reply]
On iOS, LocalStorage is limited. I often lose work when a tab reloads in mobile-editor, VE, NWE, etc. But in the classic editor, I get prompted to resubmit the form and can recover to the last preview. Preview early, preview often. This is one of the major factors that keeps me on the classic editor over the alternatives. Pelagic (talk) 09:54, 18 December 2020 (UTC)[reply]
The classic mobile editor does not have auto save. We use sessionStorage for VE/NWE. I’m surprised that reloaded tabs in iOS are not recovering. I would file a task about that if you can reproduce it. ESanders (WMF) (talk) 13:58, 24 December 2020 (UTC)[reply]
Support Definitely supporting that feature. I had an issue once during editing and I had to refresh the page which made me lose my precious time that I spent on editing in my own wiki. That feature would also be beneficial to Wikipedia users. MarioSuperstar77 (talk) 18:47, 8 December 2020 (UTC)[reply]
Support Also, please dont disable the save button in visual editor for network failures during save. Its yust stupid neding to add a dummy space somewhere yust to be able to save the edit. If you realy want to do that, maybe keep track of how often the current edit failed to save, and only do that for more permanent failures Victor Schmidt (talk) 19:59, 8 December 2020 (UTC)[reply]
Support Sure. I had countless minor edits gone due to crashes but there's once I am really angry as I had almost an 丙级 (en:C Class) article gone at the moment the network crash, I spent almost 4 hours on it. Some recovery tool will be good. I had also several near misses too, thankfully my cache is still there. Camouflaged Mirage (talk) 20:03, 8 December 2020 (UTC)[reply]
Support Yes! Please! and although I know this suggestion is "different", but edits can maybe identified by some sort of session (like an etherpad session) where also multiple editors can work when invited. this might be too much changes to the way edits are stored in the database and the such; but it would be great if that would be the trajectory of this change. Uwe a (talk) 20:28, 8 December 2020 (UTC)[reply]
Support Even now, edits will sometimes, but only sometimes recover. There should be a draft version saved somewhere where it can be easily accessed and continued working on. It doesn't have to be public, it can be saved on user's computer or on WMF servers. I've lost hours of edits because of browser tab crashes and network outages. Ponor (talk) 22:00, 8 December 2020 (UTC)[reply]
Support There are similar user scripts, but native should be. It may need to be manually enabled or warned for privacy and validity. YFdyh000 (talk) 23:42, 8 December 2020 (UTC)[reply]
Support it has often happened to me that I have lost a lot of what I have written, so this would be a very nice feature. Kogge (talk) 08:35, 9 December 2020 (UTC)[reply]
Support I've installed a browser plug-in specifically because of the days of work I've lost due to not having this. I use the 2010 editor with syntax highlighting. czar17:07, 11 December 2020 (UTC)[reply]
Support Oh yes, oh yes. I've lost many entire articles because of this problem, despite using various browser add-ons that attempt to back up the contents of form fields (the lack of a specific identifier for a specific instance of the main editing window generally defeats these things, unless you strictly work on one page at a time). — SMcCandlish ☺☏¢ >ʌⱷ҅ᴥⱷʌ< 06:52, 15 December 2020 (UTC)[reply]
Support Jax MN (talk) 18:43, 8 December 2020 (UTC)