-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Allow to manage overflow within md-sidenav-layout #487
Comments
I'm not sure I follow. For me setting the height to |
👍 I'm running into a related problem. since the |
Also @hansl the |
Reason I was spinning my wheels: failure to understand some shadow DOM things related to the component and CSS scope and tag selectors. Still agree with @cortopy's assessment. |
I was just testing this issue with the alpha.5 release and my css seems to be taken into account now:
At least now I feel like I can style |
After discussing this with @robertmesserle it seems like the CSS in master would already fix this. In addition, you seem to say this is fixed as of alpha.5. I'm closing this for now, but if you think there's more work needed feel free to file a new issue or comment here. Cheers! |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
feature
The following won't work if the layout of the whole application is to take 100% of the height
If there is a Component too large within md-content, the whole page will scroll, including the sidebar if it's open and any top toolbars. In this instance, changing the css of the sidenav component to:
allows adjusting the
overflow
of children components within the main area using percentages. Percentages will not work unless the height ofmd-content
is set. The advantage of this approach is that sidenav can stay open and won't scroll. Top toolbars don't scroll either.Being able to style md-content to manage heights and widths of components within it.
Adding a
height: inherit
formd-content
fixes the issue, but I'm not sure hard coding this would be the best solution.Taking control of how scrolling affects each part of the whole layout. Currently it's an all or nothing approach
Did this work in previous versions of Angular / Material?
Material2: 2.0.0-alpha.4
Angular: rc01
The text was updated successfully, but these errors were encountered: