-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Implement new web props parity with RN core in Fabric #11185
Copy link
Copy link
Open
Labels
Area: FabricSupport Facebook FabricSupport Facebook FabricNew ArchitectureBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricWorkstream: Component ParityClose the parity gap between RNW and RN for core RN components and their supporting APIs.Close the parity gap between RNW and RN for core RN components and their supporting APIs.enhancement
Milestone
Description
Metadata
Metadata
Assignees
Labels
Area: FabricSupport Facebook FabricSupport Facebook FabricNew ArchitectureBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricWorkstream: Component ParityClose the parity gap between RNW and RN for core RN components and their supporting APIs.Close the parity gap between RNW and RN for core RN components and their supporting APIs.enhancement
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
No status
Summary
RN is trying to make it easier to share code/knowledge between React web dev and React Native dev. Part of this means implementing web props in React Native.
Upstream tracking issue: react/react-native#34424
Motivation
We need to maintain priority with RN core's props, though not necessarily for Paper as we lean into Fabric.
Basic Example
RN Core implemented aria accessibility props here: react/react-native@720cdbc
Open Questions
No response