Keep a read-only TextInput focusable on Android

[YevheniiKotyrlo]

Summary:

On Android, editable={false} disables the EditText: ReactTextInputManager.setEditable writes the prop onto View.isEnabled. A disabled view takes no focus, so a hardware keyboard's Tab skips a read-only input, TalkBack announces it as disabled, and its text cannot be selected or copied. readOnly reaches native as editable={!readOnly}, so it is the same view. On the web a readonly input keeps its tab stop, its focus and its selection and refuses only edits.

This refuses input the way TextView does instead: ReactEditText drops its key listener while it is read-only. A TextView with no key listener is no text editor, so no input method serves it, hardware keys do not edit it and cut and paste leave its selection menu, while its movement method keeps it focusable and selectable. The view stays enabled, and aria-disabled / accessibilityState={{disabled: true}} still disable it through BaseViewManager.

Two TextView behaviours follow from a missing key listener:

• getInputType() reports TYPE_NULL, so isMultiline, isSecureText and commitStagedInputType read the input type the props configured.
• TextView marks every EditText editable for accessibility and performs ACTION_SET_TEXT whatever its key listener, so the input's accessibility delegate clears the flag, removes the action and refuses it while the input is read-only.

The soft-keyboard guard checks isEditable as well, so the paths that focus an input on their own — autoFocus, the accessibility delegate's click and a long-press selection — raise no keyboard for a read-only input. focus() keeps its contract: TextInputState.focusTextInput still refuses a non-editable input (#30695).

Related: #7437, #30597.

Changelog:

[ANDROID] [FIXED] - A TextInput with editable={false} or readOnly keeps its focus, its tab stop and its text selection

Test Plan:

• ReactTextInputPropertyTest: on main, testEditable, testNonEditableTakesFocus and testNonEditableRefusesAccessibilitySetText fail; with this change the class passes (34 tests). New cases cover refused hardware keys, the refused ACTION_SET_TEXT, and the keyboard type, multiline and secure entry kept across a read-only window.
• ./gradlew :packages:react-native:ReactAndroid:testDebugUnitTest -Preact.internal.useHermesStable=true passes (769 tests), and node ./scripts/format-kotlin.js --check is clean.
• RNTester on a stock Android 16 emulator: a hardware Tab walk stops on a read-only input, and a long press selects its text with Copy offered and no Cut or Paste. The before/after recordings are in the comment below.

[YevheniiKotyrlo]

Device evidence — before / after

UNFIXED — from touch mode, the first Tab focuses the First box and the second passes over the read-only TextInput to the Last box; a long press on the input's first word selects nothing.

FIXED — the second Tab stops on the read-only input, and the long press selects the word, offering Copy and no Cut or Paste.

before — main, 96dddb0feb	after — with this PR

Screen recordings of RNTester debug builds of main and of this PR's head on an Android 16 (API 36) emulator, 1140×2400 at density 480. In the first row Tab is pressed twice from touch mode in a scene of two Pressables with a TextInput that has editable={false} between them, above a line naming the one that holds focus; in the second row the same kind of input is long-pressed on its first word, above a line showing the selection onSelectionChange reports.