Skip to content
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

Jump to bottom

Implement accessibilityState: busy property for Modal for fabric #13054

Closed
jonthysell opened this issue Apr 29, 2024 · 0 comments · Fixed by #13952
Closed

Implement accessibilityState: busy property for Modal for fabric #13054

jonthysell opened this issue Apr 29, 2024 · 0 comments · Fixed by #13952
Assignees
@chiaramooney
Labels
API: Completion Area: Accessibility Area: Component Views Area: Fabric Support Facebook Fabric Area: Modal Area: View Props https://reactnative.dev/docs/view#props enhancement New Architecture Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric Parity: Fabric vs. Paper RNW Fabric does not look or behave like RNW Paper Workstream: Component Parity Close the parity gap between RNW and RN for core RN components and their supporting APIs.
Milestone
Next

Comments

@jonthysell
Copy link
Contributor

jonthysell commented Apr 29, 2024 •
edited by chiaramooney
Loading

Implement the accessibilityState: busy property for the fabric implementation of Modal.

Note: The state disabled was already implemented by #11674,but the remaining property values (selected,checked,busy,and expanded) need to be implemented.

This property was available in RNW Paper via FrameworkElementViewManager.

See #13327 for implementation details.

See https://reactnative.dev/docs/accessibility#accessibilitystate for details.
@jonthysell jonthysell added API: Completion Area: Accessibility Area: Component Views Area: Fabric Support Facebook Fabric Area: Modal Area: View Props https://reactnative.dev/docs/view#props enhancement New Architecture Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric Parity: Fabric vs. Paper RNW Fabric does not look or behave like RNW Paper labels Apr 29, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) label Apr 29, 2024
@chrisglein chrisglein added this to the Backlog milestone Apr 30, 2024
@chrisglein chrisglein removed the Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) label Apr 30, 2024
@chiaramooney chiaramooney added the Workstream: Component Parity Close the parity gap between RNW and RN for core RN components and their supporting APIs. label Oct 3, 2024
@chiaramooney chiaramooney self-assigned this Oct 9, 2024
@chiaramooney chiaramooney modified the milestones: Backlog, Next Oct 9, 2024
@chiaramooney chiaramooney mentioned this issue Oct 9, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chiaramooney chiaramooney

Labels
API: Completion Area: Accessibility Area: Component Views Area: Fabric Support Facebook Fabric Area: Modal Area: View Props https://reactnative.dev/docs/view#props enhancement New Architecture Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric Parity: Fabric vs. Paper RNW Fabric does not look or behave like RNW Paper Workstream: Component Parity Close the parity gap between RNW and RN for core RN components and their supporting APIs.
Projects
RNW New Architecture
Status: Done
Milestone
Next
Development

Successfully merging a pull request may close this issue.

Add Support for AccessibilityState:Busy chiaramooney/react-native-windows
3 participants
@jonthysell @chrisglein @chiaramooney