Repository navigation
Conversation
This branch has not been deployed
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.
Fixes #5258
Documents the
priorityoption ofannounceForAccessibilityWithOptions(), added in React Native 0.84. The docs listed onlyqueue.The signature becomes
options: {queue?: boolean, priority?: 'low' | 'default' | 'high'}, and the parameters table describes each value with the JSDoc wording fromAccessibilityInfo.js. The option is marked iOS only, because the Android implementation ignoresoptions.Changed in
docs/accessibilityinfo.mdand inwebsite/versioned_docs/version-0.84throughversion-0.87. Version 0.83 and older do not havepriority.Two choices you may want changed:
<hr/>, as inshare.md. They could move into the paragraph above the table.priorityonly on iOS 17 and later. I kept to the JSDoc wording and left that out. I can add an "iOS 17+" note.