User Interface (UI) / User Experience (UX) · Articles & templates · Created by
Scrolls Terminal
declined
There used to be a manual save button in addition to the auto-save that we currently have. The current feature is great, except when I need to leave an article in a hurry and I am not sure if it will have time to autosave, so I wait the five seconds to ensure autosave has caught edits, causing uneccesary time wasteage.
Adding the save button back would give us peace of mind that the save process had been initiated once we are done editing and that we can safely leave the page. It restores more control to the human writing the article.
Follow up
Just to follow up on a couple of these counter points. I have personally lost data due to the autosave and have had to go back and double work because of it (I spent two hours last night correcting articles that had not saved the last mention article in a list last night in fact), and for those saying just type one character and then delete it, that is two button presses and associated movement without confirmation as opposed to one and associated movement with confirmation
... This is to follow up on the follow up. the last part should have said one press of the save button. The inclusion of parenthesis caused the bold, and exception of my statement about the save button.
The UI update did not address this issue, I am having to do double work constantly to ensure what I input into the system is kept.
The system might be saving every 350 milliseconds, but that is not how long it takes out here in the world to get a response for some of us. I can easily sit here for five seconds waiting for a saved response from the server after inputting and deleting characters to trigger the save, which is a ridiculous replacement for the save button. Additionally, sometimes after receiving a saved response my mentioned articles still don't show up with links in the article, so this system from my perspective is a step backwards from the basic functionality of the save button where I did not have these issues.
The Team's Response
Thanks for your suggestion! We know that there were issues with the auto-save, but UI update has addressed them. The save button will not be coming back, and as we update other parts of the website, it will eventually disappear from other locations as well.
For those which save anxiety (a totally understandable and relatable feeling), be aware that the timer between saves is
not 5 seconds, it's 350 milliseconds (i.e. it attempts to save almost 3 times per second). On the top right, under the "View/Preview" buttons, there is a timestamp that updates every few seconds to let you know that the auto-save is going through.
Additionally, if the save fails, you will be warned by the system: if you have been disconnected (either because of a local problem or because the server's down), a pop-up will appear and prevent you from writing until you reload. The pop-up appears immediately after a save fails, which means that it will appear 350 milliseconds after the last save at the latest (which means that the page is safe to reload without losing work). On the other hand, if you used a special character (such as an unsupported emoji), a red error will appear at the top right as well.
Please keep in mind that World Anvil is not designed to be used on multiple tabs or devices at the same time. Doing this might cause data loss if you have the same article open for editing in two different places.
If you encounter issues with the autosave that are not covered by the two error messages I mentioned, please
report them as bugs.
Current score
62/300 Votes · +11904 points