Thomas Bruederli wrote:
Charles McNulty wrote:
Is this feature request to store drafts in localstorage defined in any detail anywhere? Is it partially implemented anywhere, or part of a plugin? I looked and couldn't find anything other than a couple of messages in the dev archives.
No, this isn't implemented or started yet.
Now we have a start in latest git master.
The storage is yet unencrypted but ready to do some first testing.
Whenever one leaves the compose screen "intentionally", the copy in local storage is removed. One is supposed to save the compose state as draft. Also when somebody logs out (by hitting the "logout button), I take this as an intentional action and clear the entire compose storage for this user. Only in cases where you quit the browser (and thus the session) in other ways or if the server loses the session data, the local copy remains in the browser's storage. When you then re-login an open the compose screen again, a dialog will ask you whether to restore the locally saved message contents.
Along with the local storage, I also tried to improve the general behavior on session timeout or other unexpected errors when the client communicates with the server.
Everybody is invited to give it a try with git master. Probably the behavior when to keep data and when to ask to restore is subject for improvements. I'm waiting for your feedback on this.
Kind regards, Thomas