You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[iOS] BottomNavigation with custom TabStrip is "cutting" any scrollable content #8220
It seems that the grid-wrapping solution above is not working when we have a page-router-outlet as tab content. For example the issue is present when there is a large scrollable content in one of the page-router-outlets as shown below
We found that the issue is related to this "simple" rule and is caused by the NSEmptyOutletComponent used in Angular when there is lazy loaded modules. It renders a Frame which is not wrapped in a layout and the result is that it sometimes gets its dimensions wrong.
There is an easy workaround - implement and use a custom version of NSEmptyOutletComponent. The approach is shown in this repo. The custom empty outlet implementation (and usage in the routing module) is in this commit.
Activity
NickIliev commentedon Jan 6, 2020
The solution is to wrap the BottomNavigation in an additional layout.
Playground demo here
NickIliev commentedon Jan 8, 2020
It seems that the grid-wrapping solution above is not working when we have a page-router-outlet as tab content. For example the issue is present when there is a large scrollable content in one of the page-router-outlets as shown below
NickIliev commentedon Jan 14, 2020
This issue seems closely related to the above behavior
vakrilov commentedon Jan 20, 2020
We found that the issue is related to this "simple" rule and is caused by the
NSEmptyOutletComponentused in Angular when there is lazy loaded modules. It renders a Frame which is not wrapped in a layout and the result is that it sometimes gets its dimensions wrong.There is an easy workaround - implement and use a custom version of
NSEmptyOutletComponent. The approach is shown in this repo. The custom empty outlet implementation (and usage in the routing module) is in this commit.NickIliev commentedon Feb 3, 2020
Issue moved to NativeScript/nativescript-angular #2116 via ZenHub