[Frontend] Shelf tonight-notes: the auto-save debounce is cancelled on unmount without flushing #536

New issue

Open

opened 2026-09-06 20:03:13 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-09-06 20:03:13 +00:00

Contributor

Found while doing #464.

TonightNotes in webapp/frontend/src/pages/SessionShelf.jsx (around lines 234–236) auto-saves on a 1.5 s debounce (#410) and clears the pending timer on unmount without flushing it. Navigating away within 1.5 s of the last keystroke therefore loses those characters today: the timer is cancelled, the save never fires, and nothing asks.

Adding the new in-app prompt (useUnsavedChangesPrompt, #464) there would only surface the loss, not prevent it: accepting the confirm still discards. The right fix is to flush the pending save on unmount (and on beforeunload, with navigator.sendBeacon or a synchronous path if the API allows), after which the prompt becomes near-unreachable on that field and is not needed.

Severity: low in practice (the window is 1.5 s, the field is a GM's live notes), but it is a genuine data-loss path in a milestone line whose promise is that data is never lost.

Acceptance:

Unmounting TonightNotes with a pending debounce writes the pending text before the component goes away.
A test that types, navigates within the debounce window, and asserts the save request was made with the final text; confirmed to fail without the flush.
BeatNotesEditor (:59) is a straightforward candidate for useUnsavedChangesPrompt if wanted; decide in the same change.

Found while doing #464. `TonightNotes` in `webapp/frontend/src/pages/SessionShelf.jsx` (around lines 234–236) auto-saves on a 1.5 s debounce (#410) and clears the pending timer on unmount **without flushing it**. Navigating away within 1.5 s of the last keystroke therefore loses those characters today: the timer is cancelled, the save never fires, and nothing asks. Adding the new in-app prompt (`useUnsavedChangesPrompt`, #464) there would only surface the loss, not prevent it: accepting the confirm still discards. The right fix is to flush the pending save on unmount (and on `beforeunload`, with `navigator.sendBeacon` or a synchronous path if the API allows), after which the prompt becomes near-unreachable on that field and is not needed. Severity: low in practice (the window is 1.5 s, the field is a GM's live notes), but it is a genuine data-loss path in a milestone line whose promise is that data is never lost. Acceptance: - [ ] Unmounting `TonightNotes` with a pending debounce writes the pending text before the component goes away. - [ ] A test that types, navigates within the debounce window, and asserts the save request was made with the final text; confirmed to fail without the flush. - [ ] `BeatNotesEditor` (`:59`) is a straightforward candidate for `useUnsavedChangesPrompt` if wanted; decide in the same change.

claude-bot referenced this issue

2026-09-06 20:03:38 +00:00

fix(frontend): warn before an in-app navigation discards an unsaved edit (#464) #537

claude-bot referenced this issue

2026-09-06 20:04:27 +00:00

[Frontend] Warn before an in-app navigation discards an unsaved edit (needs a data router) #464

claude-bot referenced this issue

2026-09-06 20:21:54 +00:00

[Frontend] Adopt the React Compiler lint rules from eslint-plugin-react-hooks v7 #182

claude-bot referenced this issue

2026-09-06 21:03:12 +00:00

v4.4.0 build order: UX Overhaul in six phases, with two review checkpoints #535