Put simply, I hate CSS resets. I think they a horrible practice and if used then an understanding of the cascade is missing. If you have a browser issue to an element of nines own CSS then correct it in your style or fix as necessary. Odds are if a reset is used than a style being applied by the set is gang to be overwritten by ones own CSS again. Then what is the point? I have been developing for web professionally going on four years and have never had to use a reset. Even with support of IE6 and IE7. Even the different by models can be handled with minimal effort (usually).

Though I have not used it myself a good option for just trying to cover the cross browser issues would be Normalize CSS. Unlike Eric Meyer’s reset all margins are set to a greatest common denominator across browsers to make things act the same across browsers. This is a much smarter way to handle a “reset”. With a typical reset it is often that an element may even have it’s height and width set to zero which can cause an element to not appear correctly without more CSS. If the developer is not familiar with what the rest is actually doing than some element may be lost in the end and can cause a problem for future expansion.

When it comes down to it a reset is another style sheet to be included, another http request or another hundred or more lines at the beginning of a CSS file. When styles are ultimately going to be written again that is a significant enough factor for me to want to exclude using a reset. If you want standardization for cross browsers use normalize if you really feel it will save a lot of work or be beneficial. Otherwise shift your focus towards your approach to CSS and due diligence in browser checks. Responsive web is where we should be moving towards which means our web should be adapting to the browser and device anyway. Pixel for pixel across browsers is becoming less of a trend and that is so because that s where the web is shifting.