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
Is normalize.css required? #12133
Comments
|
So the margin on the top of the navigation bar is expected? I think that looks strange. Maybe I used the |
It's expected that you'll reset it yourself. |
Thanks. At least I now know everything I did was correct, and it's only the result is not what I expected. |
I wish Angular Material had an official reset/normalization story on this aside from "we don't touch what we don't own", which in any case I could only find by digging into github issues. Is there one I don't know of? Even if not prescribed in actual code then at least in best practices and recommendations someplace in the doc. This might be obvious to an experienced/knowledgeable material dev, but it is not at all obvious to a noob how global styles might adversely effect material's styles for example. I chose angular so I didn't have to worry about details like this. Maybe I'm overthinking it, but I dislike the uncertainty, and hours of searching online have not yielded and concrete answers. |
@polypus74 What did you decide to use at the end? |
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:
Maybe a bug.
What is the expected behavior?
When creating a
material-nav
component, the menu and the navigation bar should align correctly.What is the current behavior?
There's a margin at the top of the title bar, but no margin at the top of the menu bar.
What are the steps to reproduce?
I asked a question at https://stackoverflow.com/questions/51258963/angular-material-navigation-bar-not-aligned/51259364?noredirect=1#comment89501187_51259364, and it was solved. But I think it might be a bug.
What is the use-case or motivation for changing an existing behavior?
Want to know if it is really a bug.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: