You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 597f74c
Browse filesBrowse the repository at this point in the historyBrowse files
fix(web): a stale queued-edit save no longer clears a newer edit
#24972 moved queued-message edits into a shared store so they survive
navigation, but the save lock stayed in the chat view. Repro:
1. Start a slow save of a queued edit.
2. Navigate away from the thread.
3. Come back and edit the same message again.
4. The first save finishes, clears the newer edit's draft and ends it.
The remounted view had a fresh lock, and the finishing save only knew the
thread key, not which edit it belonged to.
The queued-run edit store now owns saves. startSave claims the open edit
(one save at a time, exposed through savingAtom for isSaving) and returns
a finisher bound to that edit's identity. When the save settles after its
edit was ended or begun again, the finisher changes nothing and returns
false, so the hook leaves the newer edit and its draft alone. This
replaces suspendExitWatch/resumeExitWatch; the rest of the design is
unchanged.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments