docs: explain iOS 26 keyboard avoidance - #569
Draft
thiagobrez wants to merge 1 commit into
Draft
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
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.
Summary
useBottomTabBarHeightpattern for bottom-fixedKeyboardAvoidingViewcontent while preserving a full-screen backgroundThe initial global scene-resizing approach was rejected during adversarial review: it would break iPad/sidebar/tvOS placement, full-bleed and translucent backgrounds, minimized bars, bottom accessories, and existing consumer offsets. The final change is intentionally consumer-scoped documentation and an example.
Validation
yarn lint(passes with 3 existing warnings)yarn typecheckyarn buildyarn build:iosyarn build:androidy=803.67baseline toy=720.67–770, above the tab bar aty=791; semantic tap and keyboard-open text entry passThe repository-wide
yarn testcommand has a pre-existing package with no tests, and the focused Jest fallback hits the existing React Native/Babel setup parse failure. This change adds no runtime library logic requiring a new unit seam.Closes #505