Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

CSS

Posted by Paul Jackson
Paul Jackson
8,943 Points

*[SOLVED]* Reason why my responsive design isn't working?

I'm designing a website and it seems like the responsive CSS isn't responding correctly. The responsive.css file is acting like a main.css file in that it doesn't seem to matter what width the viewport is. I use the chrome dev tools and adjust for multiple mobile screens, but whatever I set in the responsive.css file, that's what the screen does.

Some of my responsive code:

@media screen and (min-width: 500px) {

 .mobileHeader {
     display: none;
 }

 .menu,
 .menu ul {
    display: -webkit-flex;
    display: -o-flex;
    display: -moz-flex;
    display: flex;
    -webkit-justify-content: space-around;
    -o-justify-content: space-around;
    -moz-justify-content: space-around;
    justify-content: space-around;
    -webkit-flex-wrap: wrap;
 }

}

And I have this in my HTML head:

<meta name="viewport" content="width=device-width, initial scale-1.0">

Help?

Paul Jackson
Paul Jackson
8,943 Points

Found the problem...

the meta tag should read "initial scale=1.0" not "initial scale-1.0"

Adam Duffield
Adam Duffield
30,494 Points

It may sound a bit trivial but have you checked that your stylesheet is even being imported into your project? We all do it now and again no matter how experienced we are.

If that's not the case is there any chance for a little more context or code? From what I can see so far sounds like it could be a typo or caching issue? Try hard refreshing just incase?