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 }}
This repository has been archived by the owner on Aug 16, 2023. It is now read-only.
The HomeFragment and DeepLinkFragment are treated as Top-level destinations, while the FlowStepFragment, SettingsFragment and the Fragment for Shopping Cart are NOT being treated as Top-level destinations. Irrespective of how they are treated/regarded as, the Navigation Drawer and Bottom Navigation are always shown. Is this correct?
This is confusing because the toolbar icon in the destinations that are NOT Top-level, changes to Up arrow, but we still can see the Bottom Navigation (in portrait mode) and pull the Navigation drawer from the left-side (in other resolutions/qualifiers).
If this pattern is wrong according to you, please let us know how to approach and solve this, in terms of using/leveraging this Navigation component.
Regards,
Kaushik
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The HomeFragment and DeepLinkFragment are treated as Top-level destinations, while the FlowStepFragment, SettingsFragment and the Fragment for Shopping Cart are NOT being treated as Top-level destinations. Irrespective of how they are treated/regarded as, the Navigation Drawer and Bottom Navigation are always shown. Is this correct?
This is confusing because the toolbar icon in the destinations that are NOT Top-level, changes to Up arrow, but we still can see the Bottom Navigation (in portrait mode) and pull the Navigation drawer from the left-side (in other resolutions/qualifiers).
If this pattern is wrong according to you, please let us know how to approach and solve this, in terms of using/leveraging this Navigation component.
Regards,
Kaushik
The text was updated successfully, but these errors were encountered: