fix: hide trailing word chars under caret in mid-text inline preview#359
Merged
bartekplus merged 1 commit intomasterfrom Apr 14, 2026
Merged
Conversation
The mid-text inline preview mirrored the block DOM and inserted a ghost suffix at the caret, but left the remaining characters of the word under the caret in place. Acceptance consumes those characters via findTrailingToken, so the preview read "Threee dog walked the street" while acceptance produced "Three dog walked the street" — breaking the WYSIWYG invariant users rely on. Thread a resolveTrailingToken callback through the presenter that mirrors acceptance's trailing-token logic, and strip those characters from the cloned preview in both the input/textarea and contenteditable mirror paths (walking across inline element boundaries for formatted words). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The mid-text inline preview mirrored the block DOM and inserted a ghost suffix at the caret, but left the remaining characters of the word under the caret in place. Acceptance consumes those characters via findTrailingToken, so the preview read "Threee dog walked the street" while acceptance produced "Three dog walked the street" — breaking the WYSIWYG invariant users rely on.
Thread a resolveTrailingToken callback through the presenter that mirrors acceptance's trailing-token logic, and strip those characters from the cloned preview in both the input/textarea and contenteditable mirror paths (walking across inline element boundaries for formatted words).