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
Material Guidelines suggest changing BottomNavigation (horizontal + bottom) to a (vertical + left) layout on larger displays like tablets and desktop. The need for this is clear when developing for a desktop -- it's simply not intuitive to have a bottom navigation bar. While not explicitly stated in the guidelines, I believe a toolbar would slide above and cover this component.
I propose a PR for:
Adding an isVertical prop to the BottomNavigation component that defaults to false
Adding a standard vertical style that is used when isVertical=true
Larger displays, like desktop, may achieve a similar effect by using side navigation. For instance, the compact “rail” treatment displays navigational icons by default.
This excerpt complimented by an image depicting a mini-variant of the navigation drawer (scroll to mini-variant) with the following caption:
Left navigation on a larger display, such as tablet or desktop
The solution is to use the Drawer's mini-variant for tablet/desktop and BottomNavigation for mobile.
We should not add a vertical mode to BottomNavigation, it should remain specific and stay true to its name.
PR #7925 was recently approved and added the mini-variant to the Drawer. Since there is finally a solution, this case is closed.
Description
Material Guidelines suggest changing BottomNavigation (horizontal + bottom) to a (vertical + left) layout on larger displays like tablets and desktop. The need for this is clear when developing for a desktop -- it's simply not intuitive to have a bottom navigation bar. While not explicitly stated in the guidelines, I believe a toolbar would slide above and cover this component.
I propose a PR for:
Images & references
Usage section of Material Guidelines:
https://material.io/guidelines/components/bottom-navigation.html#bottom-navigation-usage
The text was updated successfully, but these errors were encountered: