Skip to content

docs(contracts): scope the iOS keyboard class claim to instantiation #3572

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thymikee merged 1 commit into from
Oct 13, 2026
Merged

docs(contracts): scope the iOS keyboard class claim to instantiation #3572

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions packages/contracts/src/android-input-ownership.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -154,8 +154,8 @@ function normalizeAndroidPackageName(value: string | null | undefined): string |
* cannot reach them; each node still carries its producing UIKit class in `role`. The table is
* exact class names only, so a near miss fails closed rather than widening what counts as
* keyboard-owned (the same discipline the snapshot geometry policy applies to private UIKit
* roles). Classes are locale-independent, unlike every label these nodes carry, and private to
* the keyboard surfaces — an app cannot host one in its own view tree.
* roles). Classes are locale-independent, unlike every label these nodes carry, and an app cannot
* instantiate them.
*
* Four ownership shapes, because "produced by the keyboard" is not one question:
* - {@link IOS_KEYBOARD_SURFACE_ROLES}: nodes the keyboard owns PER NODE, safe for geometry
Expand Down
Loading