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

HTML How to Make a Website Responsive Web Design and Testing Build a Three Column Layout

Break Points are not Showing. Please help.

Here is my code on responsive.css and below that is on the index.html. What am I doing wrong? @media screen and (min-width: 480px) { body { background: navy; } }

@media screen and (min-width: 660px) { body { background: darkgreen; }
}

<!DOCTYPE html> <html> <head> <meta charset="utf-8"> <title> Matt May | Random Hero</title> <link rel="stylesheet" href="css/normalize.css"> <link href='http://fonts.googleapis.com/css?family=Alegreya+SC:400,700,700italic' rel='stylesheet' type='text/css'> <link rel="stylesheet" href="css/main.css"> <link rel="stylesheet" href="css/response.css">

3 Answers

Taylor Plante
Taylor Plante
22,283 Points

One thing to double check is that you have the correct link to your responsive.css page in your index.html page. Have you tried applying a basic style like making the body blue (regardless of width)? Otherwise your code looks good I believe.

html <link type="text/css" rel="stylesheet" href="css/responsive.css">

Do you have the body tag?

The code should work fine unless you do not have a body tag or if you have any html element above it!

And inside your <head> tag make sure you are linking to the correct path of responsive.css.

Hello,

Sorry it took forever for me to get back to you all. I don't know if it was an issue with caching or what the issue was. The problem corrected itself after trying it in Firefox, and Safari. Lesson learned: ALWAYS cross browser test. All is well!

Thanks,

matt