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 2e0b505
Browse filesBrowse the repository at this point in the historyBrowse files
fix(mobile): apply parent caret moves and mid-mutation text on assumed composer states
An assumed controlled snapshot (selection: null) matched any controlled
selection in isComposerNativeEcho, so a parent-only caret move on the
same value was classified as an echo, serialized with selection: null,
and dropped. Echo detection now requires an exact selection match; the
wildcard stays in resolveComposerControlledEventCount so the caret move
is still stamped at the assumed revision and accepted by the editor.
Selection events can also race a text mutation on Android (the caret
moves before afterTextChanged), so their payload can carry post-edit
text at a newly acknowledged revision. Forward that value through
onChangeText so the parent draft cannot be stamped stale at the
acknowledged revision and re-applied over newer native text.
Co-Authored-By: Claude Fable 5 <[email protected]>
0 commit comments