-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Container for non-sidenav-layouts #1938
Comments
Layout component it's not even started yet. Does not have an issue tracking the status either. |
If this is covered by the layout components, then this issue should be closed. BTW, found a workaround by wrapping everything within a |
We should have something for this, but as a workaround you can simply create a css class that uses the appropriate color, e.g. .my-background {
background-color: md-color($background-palette, background);
} |
Adds the `[md-content-wrapper]` attribute which users can apply to their wrapper element, in order to provide the theme background. This is necessary, because the only element that does this at the moment is `md-sidenav-layout` and it's not something that necessarily everybody uses. It's using an attribute selector, instead of a class, in case we want to add some extra functionality to it later on. Fixes angular#1938. Fixes angular#2106.
Adds the `md-app-background` class which users can apply to their wrapper element, in order to provide the theme background. This is necessary, because the only element that does this at the moment is `md-sidenav-container` and it's not something that necessarily everybody uses. Fixes angular#1938. Fixes angular#2106.
Adds the `md-app-background` class which users can apply to their wrapper element, in order to provide the theme background. This is necessary, because the only element that does this at the moment is `md-sidenav-container` and it's not something that necessarily everybody uses. Fixes angular#1938. Fixes angular#2106.
Adds the `md-app-background` class which users can apply to their wrapper element, in order to provide the theme background. This is necessary, because the only element that does this at the moment is `md-sidenav-container` and it's not something that necessarily everybody uses. Fixes angular#1938. Fixes angular#2106.
Adds the `md-app-background` class which users can apply to their wrapper element, in order to provide the theme background. This is necessary, because the only element that does this at the moment is `md-sidenav-container` and it's not something that necessarily everybody uses. Fixes #1938. Fixes #2106.
Adds the `md-app-background` class which users can apply to their wrapper element, in order to provide the theme background. This is necessary, because the only element that does this at the moment is `md-sidenav-container` and it's not something that necessarily everybody uses. Fixes angular#1938. Fixes angular#2106.
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. |
For layouts not using the
<md-sidenav-layout>
, dark themes can not be used, as the background does not change. Due to that, the text gets invisible and form items look bad.To understand, what I mean, check out the plunkr. Basically I took your template and changed the theme: http://plnkr.co/edit/w4v95im2irvNm4dAzQ5k
I was looking for some container class or element, but wasn't lucky in finding any.
The text was updated successfully, but these errors were encountered: