fix(0.81, macos): TextInput Fabric commands - setGhostText, blur, and selection fixes#2937
Merged
Saadnajmi merged 8 commits intomicrosoft:0.81-stablefrom Apr 22, 2026
Merged
Conversation
- Add setGhostText command to Fabric TextInput native handler (was declared in JS but missing from native dispatch) - Port ghost text implementation from Paper to Fabric with proper Fabric API adaptations (NSRange selection, direct _backedTextInputView access) - Fix setTextAndSelection using notifyDelegate:YES instead of NO, matching Paper behavior to prevent spurious delegate callbacks - Add ghost text cleanup in textInputDidChange delegate - Add RNTesterPlayground test case for verifying TextInput ref and commands (focus, blur, clear, setSelection, setGhostText) - Add debug logging in setLocalRef to diagnose ref null issue - Add test assertions for setSelection and setGhostText methods Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Fix blur on Fabric: use currentEditor to detect focused NSTextField (field editor mismatch made blur a silent no-op) - Prevent ghost text from being selectable on Fabric by clearing it in textInputDidChangeSelection, matching Paper behavior - Remove TARGET_OS_OSX guard from setGhostText command dispatch (was causing compilation issues with preprocessor) - Remove temporary debug logging from TextInput.js setLocalRef - Add commented-out Paper blur fix for future testing Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Removes the RNTesterPlayground interactive test and the commented-out Paper blur fix to keep the PR focused on Fabric TextInput command fixes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Saadnajmi
force-pushed
the
0.81/fabric-textinput-refs
branch
from
bc6be17 to
9da4c7d
Compare
The command dispatch was calling [componentView setGhostText:] unconditionally, but the protocol method is only declared under #if TARGET_OS_OSX. This caused iOS and visionOS builds to fail with "no known instance method for selector". Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Ghost text insertion/removal was going through the undo manager, causing undo/redo to restore or remove ghost text unexpectedly. Wrap ghost text attributedText mutations in disableUndoRegistration/enableUndoRegistration to keep ghost text changes off the undo stack, matching Paper's behavior. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Two ghost text bugs: 1. Undo would restore ghost text as real text because the undo manager's pre-edit snapshot contained ghost text. Fix: clear ghost text in textInputShouldChangeText BEFORE the edit, so the snapshot never includes ghost text. This matches Paper's approach. 2. Ghost text persisted after blur. Fix: clear ghost text in textInputDidEndEditing, matching Paper's behavior. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Remove disableUndoRegistration/enableUndoRegistration from ghost text handling — these were corrupting the undo manager state and breaking normal undo/redo. The real undo protection is clearing ghost text in textInputShouldChangeText (before the edit), so the undo manager's pre-edit snapshot never contains ghost text. Also skip breakUndoCoalescing in RCTUITextView when ghostTextChanging, so ghost text insertions/removals don't create undo coalescing breaks. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Ghost text insertions/removals via setAttributedString: on the text storage were getting on the undo stack, causing Cmd+Z to undo the invisible ghost text change instead of the user's actual typing. Wrap the text storage mutation in disableUndoRegistration/ enableUndoRegistration specifically when ghostTextChanging, keeping it tightly scoped to avoid corrupting the undo manager state. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
vmoroz
approved these changes
Apr 22, 2026
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
2 participants
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.
Summary
Backport of #2912 to 0.81-stable.
setGhostTextcommand to Fabric: Ghost text was implemented for Paper in [iOS/macOS] [TextInput] Implement ghost text #1890 / [iOS/macOS] [TextInput] Implement ghost text #1897 (with undo fixes in Ensure ghost text doesn't appear when performing undos #2105 / [0.73-stable] Ensure ghost text doesn't appear when performing undos #2106), but the Fabric command dispatcher and component view never got the implementation. This ports the ghost text logic (insertion, removal, attributes, delegate cleanup) fromRCTBaseTextInputViewtoRCTTextInputComponentView.blurcommand on macOS Fabric:blurwas a silent no-op because it compared[window firstResponder]against the NSTextField, but on macOS the firstResponder during editing is the field editor (NSTextView), not the text field itself. Fixed by checkingcurrentEditoron NSTextField.textInputDidChangeSelectionto clear ghost text when the user changes selection, matching Paper behavior.setTextAndSelectiondelegate notification: ChangednotifyDelegate:YEStonotifyDelegate:NOto match Paper'ssetSelectionStart:selectionEnd:behavior and prevent spurious delegate callbacks during programmatic selection changes.Test plan
setGhostTextcommand works via RNTester on macOS Fabricblurcommand works on macOS Fabricfocus,clear,setSelectioncommands still work🤖 Generated with Claude Code