fix: correct cursor position when typing after fully track-deleted content #1828
+199
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ntent When all content in a text node is track-deleted and the user types new text, characters were appearing in reverse order. This happened because: 1. Each new character was inserted after the deletion span (correct) 2. But the cursor was mapped back to the original position (incorrect) 3. So each subsequent character was also inserted at the same position The fix stores the actual insertion end position in transaction meta and uses it for cursor placement when content is inserted after a deletion span.
caio-pizzol
requested review from
VladaHarbour,
artem-harbour and
harbournick
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 811dbe59e0
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
packages/super-editor/src/extensions/track-changes/trackChangesHelpers/replaceStep.js
Outdated
Show resolved
Hide resolved
harbournick
deleted the
caio/sd-1624-fix-cursor-position-after-typing-in-fully-track-deleted
branch
harbournick
pushed a commit
that referenced
this pull request
Jan 24, 2026
# [1.9.0-next.4](v1.9.0-next.3...v1.9.0-next.4) (2026-01-24) ### Bug Fixes * correct cursor position when typing after fully track-deleted content ([#1828](#1828)) ([8de1c5f](8de1c5f))
Collaborator
|
🎉 This PR is included in version 1.9.0-next.4 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When all content in a text node is track-deleted and the user types new text, characters were appearing in reverse order. This happened because:
The fix stores the actual insertion end position in transaction meta and uses it for cursor placement when content is inserted after a deletion span.