Display should not be the defining advantage of browsers. CSS for all its easy entry point is awful as a language paradim. All inheritance no compositon and massive repetition, rigidity and fragility.

The way forward? 10 more years of pain. Browser inconsistencies seem to be lessening, but the only force driving this is developer pain. sorry but thats not a good enough reason. we need to design, develop, broker and drive a better solution.

I half expect to be told this kind of setup is in progress somewhere…

comments on <i> and <b> are well-taken, also: The first thing I have to do with a reset is to get rid of the weight: normal reset on those, since (again) we see them all the time in code pasted from Word.

To my next point, is there something more behind the reason why margin, padding and borders are also being reset on inline elements (Scott and Grant Husbands have already touched the topic), or it just hold the line with the others insuring that everything is in a plain baseline?

select, input, textarea {
-webkit-box-sizing: border-box;
-moz-box-sizing: border-box;
box-sizing: border-box;
}

Select elements use the content-box in pretty much every browser. That’s why they never actually have the same size as the other elements, even if all have the same dimensions set. I also found a bug report from Firefox for this problem: https://bugzilla.mozilla.org/show_bug.cgi?id=562153

The code works from IE8 and up and all other major browsers, according to PPK: http://www.quirksmode.org/css/contents.html

“I will assure whoever that the reasons for using resets are gradually disappearing.”

That depends on the reasons people have for using them though, doesn’t it?

Personally, I use a reset just because it forces me to deliberately think about every style that I’m applying to the site. I find doing that makes my code, and my design, better.