IssueTracker

We're working with the material team to ensure that Navigation matches the new material design guidelines.

Hi everyone. What is the progress or official decision on this one?

Hey guys, is there any progress on this issue? Can we expect these features to be implemented in the near future?"

Any update on this?

We'll update the bug here when there's updates to post. Suffice it to say, there's still work to do and we're dedicated to getting it done."

Hey guys, any update on this?"

The two biggest issues and annoyances of this bug for our end users with the new Navigation library and Bottom navigation bar are:
- Changing tab with the bottom bar resets the state and backstack of the previous tab/fragment, so our users are completely losing their navigation history (this is correctly implemented in Google Photos app)
- Pressing back from the root of one tab shows the initial tab/fragment instead of leaving the app"

I'm also facing this issue. Looking forward to the update.

This solution saved my day https://stackoverflow.com/a/51684125/5246711

Facing the same issue here. Any updates?

I'm also facing this issue, are there any updates?"

Could we get any public updates on this? We're a bit left in the dark with all of these hotlists that we cannot access. What does it mean, why is Google not more public with something of such a high important as support libraries? Why is Jetpack not open source as well? I might be going on a rant here which no one is gonna end up reading, but it's frustrating to start using the new libraries provided by Google that are supposed to accelerate development. Yet it's so hugely opinionated by the developers at Google and no feedback is being sought from the people actually using it? Why can't we, the people _actually using it_, be the one working on it as well. Why can't we have an open collaboration like Kubernetes or other Google projects? Could Google start opening up a bit more like Microsoft is doing (not that they're all holy)."

Re #13 - we do read all the comments, rants or not. We'll be updating the bug when there's updates.

Feel free to check out the AndroidX source code and contribution instructions at https://android.googlesource.com/platform/frameworks/support/+/androidx-master-dev"

Looks like the bug has been turned into a feature:
https://material.io/design/components/bottom-navigation.html#behavior

"Bottom navigation behaves differently on Android and iOS. When you select a bottom navigation item (one that’s not currently selected), each platform displays different outcomes:

On Android: the app navigates to a destination’s top-level screen. Any prior user interactions and temporary screen states are reset, such as scroll position, tab selection, and in-line search.
On iOS: the destination reflects the user’s prior interaction. If the user previously visited that section of the app, they return to the last screen viewed (with its prior state preserved, if possible). Otherwise, the app navigates to the top-level screen.""

While it's interesting that they've backtracked on the default behavior, because of this:

> Default platform navigation can be overridden when needed to improve the user experience. For example, an Android app that requires frequent switching between sections can preserve each section’s state. Or, an iOS app can return users to the top-level screen (or reset their scroll position) if it better suits the use case.

I think providing an easy option to save each section's state is still worth providing as an option."