Flyout/Popup components for Fabric #11921
Labels
Area: Fabric
Support Facebook Fabric
Area: Flyout
Area: Modal
Area: Popup
enhancement
New Architecture
Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric
Workstream: Component Parity
Close the parity gap between RNW and RN for core RN components and their supporting APIs.
Milestone
Summary
On Paper, we have Flyout and Popup. Windows-only components, not part of RN core (and as such, not tracked here)
Notes from our discussion on "what to do with these on Fabric?":
See the tracking issue for Modal on Fabric
Related issues for E2E testing:
#11279
#11102
And the overall proposal (on Paper) of "should these live here?"
#4343
All this to say, we need to figure out what happens to Flyout/Popup on Fabric. Do they come over? If so, how do they change. If not, how can Modal/community cover what they solved?
Flyout
Assuming we kept the same API surface as our Paper implementation of
Flyout
(not a given), these are the APIs:Popup
Assuming we kept the same API surface as our Paper implementation of
Popup
(not a given), these are the APIs:Motivation
Migration of Paper apps to Fabric who used Flyout or Popup
Basic Example
The text was updated successfully, but these errors were encountered: