Repository navigation
docs: correct native UI adoption and fallback guidance - #312
Merged
Merged
Conversation
Contributor
Playwright test resultsDetails
|
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.
Correct three points in the Native UI adoption guides:
verticalOnlyis for limiting automatic projection to the rail.BarPlacement.inset, including an upgrade command for existing installations.webwhen Web fallback is active; usereasonfor diagnostics.Documentation only. Related to #228.
Validation: 161 existing unit tests passed, Prettier and documentation generation passed, and engineering/marketing reviews completed with no remaining findings. The Foldable requirement was checked against the published 8.3.3 package's type definitions. No simulator validation was performed for this documentation change.