-
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
Add elevation guide #2800
Comments
It would be great to have a short and simple guide on elevation in the |
agreed would be fabulous! // @EladBezalel (thx @Splaktar!) I like the simplicity of MaterializeCSS docs http://materializecss.com/shadow.html |
Mixins like |
Now we should use @include mat-elevation($zValue); |
@Splaktar Do you have a Pr in progress that I could help with or anything like that, I've got my own branch open on my fork, wasn't sure if you had started. |
@M-a-c no sorry. I had other priorities jump up and haven't had a chance to get back to this. Thank you for helping out! |
I have a problem with hundreds of elevation directives being injected in for EVERY component. Every components has CSS styles like this:
and
How do I turn this off? |
@megamindbrian You are probably indirectly including |
@willshowell Thanks for the response! I only included mat-core 1 time in my "layout.scss". I've added "layout.scss" to angular-cli.json:
I've just confirmed layout.scss is not referenced anywhere else in the project, only angular-cli.json. |
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. |
Bug, feature request, or proposal:
proposal
What is the expected behavior?
That
.md-elevation-zX
classes are documented.What is the current behavior?
No documentation exists other than within closed PR and issue comments. There are some design documents, but they aren't really designed for developers using the APIs.
What is the use-case or motivation for changing an existing behavior?
To avoid repeated questions and rejected PRs like #2212.
Is there anything else we should know?
I would like to help with this documentation, but I would like some feedback on how the team would like this to be done before I submit a PR.
Should there be a separate doc/guide for elevation that covers examples of multiple components?
Should there be examples of using elevation in each component that it applies to?
Is there a list of such components?
The text was updated successfully, but these errors were encountered: