If you edit a document property and close the tab within the 500ms save debounce, the edit can be lost. The field-save queue does flush on beforeunload, but it's an async apiFetch with no keepalive and no "leave site?" prompt, so the browser can cancel it mid-flight. Title and content don't have this problem; they go through the editor autosave that #294 already flushes and prompts on. Field edits left that path when they moved to apiFetch.
Proposed solution: shorten or drop the debounce, or mark the post dirty while a field save is in flight so #294's prompt picks it up. It goes away on its own once documents move to core-data (#298), so only worth doing if that's far off.
If you edit a document property and close the tab within the 500ms save debounce, the edit can be lost. The field-save queue does flush on
beforeunload, but it's an async apiFetch with no keepalive and no "leave site?" prompt, so the browser can cancel it mid-flight. Title and content don't have this problem; they go through the editor autosave that #294 already flushes and prompts on. Field edits left that path when they moved to apiFetch.Proposed solution: shorten or drop the debounce, or mark the post dirty while a field save is in flight so #294's prompt picks it up. It goes away on its own once documents move to core-data (#298), so only worth doing if that's far off.