On Tue, Jan 21, 2014 at 12:05 AM, Michael Heydekamp listuser@freexp.de wrote:
The local storage copy is saved ever few seconds and isn't restricted by the draft-autosave interval. I consider this feature complete now.
Well, not sure...
I closed it because there was no feedback, neither in the ticker nor on other channels. So if you find things that don't work as expected, please open new tickets for them.
But before digging deeper into any details, one question:
What should happen if in real life...
- I get a phone call during composing a message,
- walk away from the laptop and the call takes a while,
- the laptop goes into sleep mode during the call and loses connection,
- I wake up the laptop after finishing the phone call and continue
composing?
My experience is that...
the changed message is not being saved to the draft folder anymore (not even after a re-login to Roundcube), and
that I can't send the message.
But after cancelling it and hitting the "new message" button, I can restore this changed message perfectly and send it.
But I don't even know that I can continue composing and that the message will still be saved to the local storage while continuing composing in the scenario above. There is some lack of feedback.
Suggestions?
That's probably a matter of documentation, too.
And what is taking precedence - the copy in the draft folder, or the copy in the local storage, are time stamps being compared, etc. etc. ??
There's a dialog asking whether to use the local copy. Usually one can assume that the local copy is newer or the same as the draft. There's no scenario where the local copy lags behind the saved draft.
The design is still not clear to me. I also have often been surprised by the option to restore a message which has been saved to the local storage, although it had been sent successfully already.
Please describe this with steps to reproduce.
Kind regards, Thomas