Skip to content

The allowable number of md-sidenav #3329

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

Closed
ghost opened this issue Feb 27, 2017 · 7 comments
Closed

The allowable number of md-sidenav #3329

ghost opened this issue Feb 27, 2017 · 7 comments
Assignees

Comments

@ghost
Copy link

ghost commented Feb 27, 2017

Hi! Thank you for your work! The question is... sidenav 2 work fine... But when you add 3 they are all hidden. There are no errors. Version of angular 2, and the latest material. Big Thanks!

@ghost
Copy link
Author

ghost commented Feb 28, 2017

@benb7760
Copy link

From the documentation for sidenav

A sidenav container may contain one or two elements. When there are two elements, each must be placed on a different side of the container. See the section on positioning below.

@ghost
Copy link
Author

ghost commented Feb 28, 2017

Is there a way to do example 2 on the left? Tried 1 sidenav-container, all is well. But when closed, it overlaps another container, although it is hidden. Thank you for your response.

@fxck
Copy link
Contributor

fxck commented Feb 28, 2017

Just put *ngIf inside the left sidenav and show content depending on what you are opening.

@kara
Copy link
Contributor

kara commented Mar 1, 2017

By design, we only allow one sidenav per side, but it's a bad experience to fail silently. We should be throwing an error.

@kara kara added the feature This issue represents a new feature or feature request rather than a bug or bug fix label Mar 1, 2017
@mmalerba mmalerba added has pr and removed feature This issue represents a new feature or feature request rather than a bug or bug fix labels Mar 1, 2017
@kara
Copy link
Contributor

kara commented Mar 3, 2017

Error thrown in #3369

@kara kara closed this as completed Mar 3, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants