Just noticed when looking at new PRs, probably didn't mean to include this.

👍 thanks ^^

Removing currentEntry.fragment while animation is not completed will trigger problems with application restore.

Actually, this fixes an issue with application restore. In the scenario - Tabs - Frames - Pages - all of the Frames fragments are restored before the Tabs fragments are recreated and they try to load their pages before they have been selected. The solution we came up with is to remove the Frame fragment on unload of the frame. A new problem came up - on suspend the Frame is unloaded after saveInstanceState, so the fragments are not really removed according to Android and it tries to recreate them on resume. That is why we set the currentEntry's fragment to null, so that on fragment create we can set it's contents to null, making it a non UI fragment. When the Frame is then loaded it will create a new fragment for the page.

Basically, we want the Android to re-create the Tab fragment, which loads its Frame which creates a new fragment for the Page. I'm open to other ideas.

I couldn't reproduce the problem that nullifying the fragment was supposed to fix, so I removed it 👍

You need to match restored fragment to Page or TabItem otherwise you will have a blank pages in some cases when application is restored.

This is connected to the currentEntry fragment assigned to null. It handles this case.

if frame.isLoades is false will only make page load later and it will break page transitions (pages will be empty)

Can you share a test case, so that I can check the problem?

This will load several views (before and after the selectedIndex). The whole point was an improvement so that we fire loaded only for the current selectedIndex.
Firing loaded may trigger another events like navigation, etc...

Unfortunately, for Android we have to load as much views as the ViewPagerAdapter creates. Otherwise the swipe gesture of the TabView shows blank page before the navigation is completed. CanBeLoaded is assigned by the ViewPagerAdapter instantiate item method. We have also enabled androidOffscreenLimit to be equal to 0, which enables the scenario you talk about. The idea is to have it 0 when the TabView is on the bottom and there is no swipe to navigate.