opened
dblachut-adb
username_0
### Current Behavior
```
TabNavigator({
  A: { screen: A },
  B: { screen: B },
  C: { screen: C },
  D: { screen: D },
  E: { screen: E },
}, {
    initialRouteName: "B",
    animationEnabled: true,
    swipeEnabled: false,
    navigationOptions: {
      tabBarVisible: false,
    },
    lazy: true,
  },
);

```
When the app starts and the `B` screen is displayed after using `navigation.navigate(D)` during the screen transition animation the white `C` screen is displayed for a split of a second. This is due to `C` not being loaded yet as I am using `lazy: false` flag.

### Expected Behavior
It would be nice if the screen would transition from `B` to `D` directly without showing screens that are located between them. Please note that this still may be problematic if used with `lazy: false` - when e.g. screen `C` would differ much from `B` and `D` the user could still observe the transition and it may not be desired is case the app is using its own navigation bar.

### How to reproduce
Use the screen configuration I have provided.

### Your Environment

| software         | version
| ---------------- | -------
| react-navigation | 1.5.11
| react-native     | 0.55.3
| node             | v9.2.0
| npm     | 5.5.1
Transition between not loaded screens in TabNavigator displays white page during animation
issue
created
brentvatne
username_1
hi there. the example you pasted is not runnable. please create a full example on https://snack.expo.io/ so we can run it and see what you mean.
comment
created
dblachut-adb
username_0
Hello, thank for the reply. Are you sure that description in words is not enough in this case? I guess I will try to prepare it later on.
comment
created
dblachut-adb
username_0
@username_1 Okay :+1:, I have updated the issue, please take a look.
comment
created
dblachut-adb
username_0
@username_1 could you please take off the "needs repro" flag?
comment
created
brentvatne
username_1
thanks for updating it. this issue isn't really valid anymore because in 2.0 we removed `animationEnabled` on tab navigator. this isn't a common use case and we aren't interested in supporting it, if you'd like to implement this behavior you can create your own custom navigator to do so. you can simply fork one of the existing tab navigators and make the appropriate changes to do so. I'm sorry I don't have a better answer for you :(
comment
closed
brentvatne
username_1
issue
created
dblachut-adb
username_0
No problem, thanks for taking a look and a detailed explanation!
comment