Fails media query test - it very obviously has media queries in it.
Other stuff
can’t seem to get the menu items in a row. I think it has to do with ul not being recognized as a nested element. See line 117 css for notes. And while you’re working on that problem (THANKS!) there’s a similar issue on line 72 css
I really don’t want my main body to scroll under the fixed navbar. When I click the navbar menu items, it takes me to the right place, but you can tell the top of it is still under the header bar because only part of the words are showing. I tried setting a margin-top to the main section (line 24 css), but that didn’t seem to do anything.
Thanks for any help you can provide. I realize the line numbers will move, so I added comments in the vicinity.
CSS doesn’t support nesting. When CSS sees something it doesn’t understand it simply ignores it. Either flatten your CSS or switch to SCSS (gear symbol left to CSS).
I looked at your code and found the problem for /@Media …
can you guess? Look at the rule above your at media rule…
Do you notice something wrong with it? I did.
It was actually a nested rule, so it doesn’t take a closing tag right before it. That’s why changing to SCSS fixed it. All my media inquiries are nested. In regular CSS, it definitely wouldn’t pass without closing the previous one. Thank you so much for looking and replying. I’ve learned a lot from this thread already!
Thank you @IAmRC1 and @jenovs. It seems the issue was that I was working in Edge. It won’t pass in Edge but it will pass in Chrome. Chrome is my preferred, but I’m trying to give Edge a chance. Strike 1!
@tammt - you and me both! Someone mentioned it on this thread. I had read that CSS didn’t do nesting, but saw that the example landing page did. I never figured it was something that we hadn’t learned. @IAmRC1 and @jenovs - those are both extremely useful bits of info. Thanks!
