[MlMt] Draft saving

[Muster Hans]

On 5 Jan 2015, at 21:43, Benny Kjær Nielsen wrote:

>
> Actually, drafts are always autosaved regularly in the background 
> without changing the saved state of the message. Ideally, the saved 
> state should only change when the user explicitly saves the message, 
> but
> for technical reasons I'm currently forcing such a save whenever the 
> “structure” of the message
   ^^^^^^^^^^^^^^^^^^^^^^
> changes. This happens, for example, when Markdown to HTML generation 
> is needed.

The forcing of a save sounds like the real cause of the problem here.

-- 
Paul Sture