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
Thanks @jmstout. If this is true, then it makes sense. I realized the flaw in my logic: I was pondering the navbar being on top for a screen that didnt scroll so it seemed natural. If the screen did scroll, the navbar would go away unless you have the absolute positioning. Not sure how I overlooked that. Going to close.
📢 For anyone else ending up on this still (like me) an easy way to reverse the order is to simply add flexDirection: 'column-reverse' to the Navigator.
facebook
locked as resolved and limited conversation to collaborators
May 29, 2018
I just implemented a
Navigator
component with a customnavigationBar
. When it renders, the navBar renders at the bottom of the screen, but otherwise renders correctly. I noticed that this is because in the code, navBar renders after the scene: https://github.com/facebook/react-native/blob/master/Libraries/CustomComponents/Navigator/Navigator.js#L1318-L1321I noticed that
Navigator.NavigationBar
gets around this by setting the navBar component toposition: absolute
(https://github.com/facebook/react-native/blob/master/Libraries/CustomComponents/Navigator/NavigatorNavigationBar.js#L190-L195)Would it make sense to have the navbar render first so that it was at the top by default? I can turn open a PR if so.
The text was updated successfully, but these errors were encountered: