Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cascading navigation drawer #5944

Open
clement-hollander opened this issue Jul 21, 2017 · 5 comments
Open

Cascading navigation drawer #5944

clement-hollander opened this issue Jul 21, 2017 · 5 comments
Labels
area: material/sidenav feature This issue represents a new feature or feature request rather than a bug or bug fix P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@clement-hollander
Copy link

Looking at the Navigation Pattern docs, it's allowed to have a cascading navigation drawer on Desktop : https://material.io/guidelines/patterns/navigation.html#navigation-patterns

The MdSidenav works great at the first level, but anybody has dealt with it ? What would you recommend ? Or has the team previewed to handle that ?

@donroyco
Copy link
Contributor

See #119. Please use the search function.

@clement-hollander
Copy link
Author

@donroyco thanks but I meant "Cascading navigation drawer" detailed here : https://material.io/guidelines/patterns/navigation.html#navigation-patterns not "Cascading menu support"

@willshowell
Copy link
Contributor

@clement-hollander I personally haven't seen that discussed here before. I think @jelbourn
and @mmalerba are planning to do some refactoring of the sidenav to improve the api, so perhaps something like this will be considered.

@mmalerba mmalerba added the feature This issue represents a new feature or feature request rather than a bug or bug fix label Jul 21, 2017
@mmalerba mmalerba self-assigned this Jul 21, 2017
@mmalerba mmalerba added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label Nov 21, 2017
@angular-robot
Copy link
Contributor

angular-robot bot commented Feb 1, 2022

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

@angular-robot
Copy link
Contributor

angular-robot bot commented Feb 21, 2022

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: material/sidenav feature This issue represents a new feature or feature request rather than a bug or bug fix P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
5 participants