Brooklyn Nicholson 92f62bedd7 fix(desktop): extend the composer undo stack to the message edit composer ... The edit composer pastes through the same `insertComposerContentsAtCaret` the main composer uses, so it had the identical bug: the Range-based insert never reaches Chromium's undo stack and Cmd+Z skipped past the paste to destroy the edit before it. Its inline-ref and trigger-chip inserts mutate the DOM directly too, with the same result. Both surfaces now share `useComposerUndo`. The hook already keys its document-level `beforeinput` claim off `document.activeElement`, so the two mounted instances stay independent — only the focused editor's stack responds. Undo/redo is handled ahead of Escape here, since a stray Cmd+Z falling through would cancel the whole edit rather than step back one change. `insertRefStrings` banks through `withUndoPoint` rather than recording after the insert, which would have snapshotted the state it was meant to restore.		2026-07-26 18:21:50 -05:00
..
bootstrap-installer	fix(installer): stamp the bootstrap-complete marker from the Rust installer	2026-07-26 16:02:13 -05:00
desktop	fix(desktop): extend the composer undo stack to the message edit composer	2026-07-26 18:21:50 -05:00
shared	feat(billing): carry the payment-method union through to clients (#71542)	2026-07-27 01:49:43 +05:30