react-navigation / react-navigation/react-navigation.github.io
Issue with `Opening a Full Screen Modal`?
@brentvatne is already working on this.
Since Feb 15, 2018.
- Dominant language
- JavaScript
- Stars
- 324
- Forks
- 2k
- PR merge metrics
- No merged PRs in 30d
Description
The website documentation has a section on "Opening a Full Screen Modal" (here).
The method described is to have two child Stack Navigators with a shared parent. The children are created with mode: "modal" and mode: "card", respectively.
Given this setup, let's assume a user opens an app to a card Screen. As soon he navigates to a modal screen, wouldn't the modal StackNavigator contain an unwanted screen at the root of its stack -- the screen that StackNavigator created by default as the initial route? Of course it's possible to provide an initialRouteName, but in this scenario, it doesn't make sense to do so. The modal navigator's screens are not meant to be shown in succession, and hence, this navigator has no conceptual initial route.
Is there a way to address this that I am missing? It seems like the documented approach would create problems with back behavior given the existence of the initial screen at the root of the modal StackNavigator.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.