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
The bottom nav bar example demonstrates the usage of the NestedRouter() with an AppBar() Widget. Selecting the NavBar Item 'History' e.g. will select the item and leads to this url: .../bottom-nav-example/history-view. After refreshing the browser, the url is still the same as expected and also shows the HistoryView but the favorites icon is selected.
To reproduce
Run router_example
Navigate to history view via the app bar item
Refresh the browser
HistoryView is shown but Favorites Icon is selected
Expected behavior
Since there are many scenarios where Nested Routing is used with an appbar the expected behavior in web would be to see the correct nav bar item selected.
Screenshots
Additional Context
No response
The text was updated successfully, but these errors were encountered:
@mraaz97 yes, I actually saw this when I migrated the web app. It can be fixed using exactly this technique to get the url path id and match it with the tab.
When we get some time we will update the example to include this information. Thank you for creating the issue. It will help make sure it doesn't slip through the cracks.
Describe the bug
The bottom nav bar example demonstrates the usage of the
NestedRouter()
with anAppBar()
Widget. Selecting the NavBar Item 'History' e.g. will select the item and leads to this url:.../bottom-nav-example/history-view
. After refreshing the browser, the url is still the same as expected and also shows theHistoryView
but the favorites icon is selected.To reproduce
Expected behavior
Since there are many scenarios where Nested Routing is used with an appbar the expected behavior in web would be to see the correct nav bar item selected.
Screenshots
Additional Context
No response
The text was updated successfully, but these errors were encountered: