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!
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
When to use CSS Reset Method
So should we always use a CSS Reset Method and if not, when should it be used?
John Grillo30,241 Points
One way to look at it is if you're doing a large project, like the Oregon Health Plan site, then reset.css is the way to go as you're leaving nothing to chance. You're nuking it and rebuilding upon the ashes.
Normalize.css assumes that you're zeroing out the more common elements bu still want to preserve the useful ones, like tables and <input> for example. Normalize.css, based on my experience and my web dev teacher, is that it tends to make things look and act like they do in Google chrome. I've made one or two websites where it didn't quite work out if I used firefox or opera instead, but I think this will be a rarity. For the majority of your uses, you should be ok with Normalize.css
Chris McKay2,401 Points
Yes you should always use a reset method.
Due to lack of standards around it, each browser manufacturer creates their own styling for their browser, leaving each browser's default base rendering of elements different. This, of course, causes inconsistencies across browsers that must be fixed. - http://pointnorth.io/#styling
So I should always use reset and normalize? It seems to me that using Normalize only can be just as effective.