Save editor content after timeout

[Brian Teague]

Current state:
1. Create a new task; set its name, wait 10 seconds, internal title of the task is "(no title task)"
2. Type "one" into the body. Wait 10 seconds, title of the task is "A new task" without set content
3. Type "two" on the next line of the body. Wait 10 seconds, the content is "One\nT"
4. Close GTG. the full task has been saved.

Expected behavior:
The correct behavior should be that after some timeout when a task is not written, the content is saved. If you don't press anything for a second (and you made changes), save the content. Or maybe when the window loses focus, save changes.

[Brian Teague (bteague)]

Note: Closing the task (instead of quitting GTG entirely) also results in the full task being written to the backend.

I'm not a hair-on-fire kind of bug reporter, but if GTG crashed before you closed the task, this could result in data loss.

[Izidor Matušov (izidor)]

I can confirm this behavior and I can agree it is bad. However, it is only a matter of editor. Try to change e.g. a due date from the browser from the context menu - the changes are reflected immediately.

[Izidor Matušov (izidor)]

Can you confirm that?

[Brian Teague (bteague)]

Confirmed. The problem seems to be isolated to the "content" field of the editor; changes to the metadata (due data, subtasks, tags, etc), made either in the editor or the browser, are reflected immediately.

[Lionel Dricot (ploum-deactivatedaccount)]

This is not a bug but a feature : there's a timeout of a few seconds to avoid saving the content at each and every letter typed.

The possible data loss (which already happened to me in testing) is then only limited to a few characters or one sentence at worst.

[Izidor Matušov (izidor)]

Lionel > No, it is a bug. Imagine a following use case (which happened to me several times):

You open a new task and write down the title of the task (without pressing <enter>). Switch to the browser to find more details and forget about the task. In the evening restart computer without closing the task. The next morning, you find a "(no title)" task :/

The correct behavior should be that after some timeout when a task is not written, the content is saved. If you don't press anything for a second (and you made changes), save the content. Or maybe when the window loses focus, save changes.

[Lionel Dricot (ploum-deactivatedaccount)]

Ah, ok. I understand. And, indeed, I remember this bug. We should then have something periodically checking for open tasks and, if modified and unsaved, saving them.

[Izidor Matušov (izidor)]

I updated title & bug description