One of the big things I like about CSS resets is it forces me to think about every design decision rather than just going with the 'sensible' browser defaults.<p>I guess with discipline I can train myself to always think about things like the rhythm created by font-size and margins on headers, but I've not experienced the downsides of a full reset yet.
I use it indirectly (via Twitter Bootstrap) and I have no complaints.<p>I found it a bit curious though that they don't dogfood it on their Github page (<a href="http://necolas.github.com/normalize.css/" rel="nofollow">http://necolas.github.com/normalize.css/</a>), but I guess that's not a huge deal or anything.
Perhaps I am missing something here. I looked at the demo page in FF10, Chrome17, and IE 8, and I see different spacing in rendering across those platforms (mostly in IE8, but FF10 and Chrome17 are not the same either)<p><a href="http://i.imgur.com/SMwHD.png" rel="nofollow">http://i.imgur.com/SMwHD.png</a>
I have been using normalize for the past few months in all of my new projects and I can attest to its superiority over the standard resets. Great work, as ever, necolas.
Doesn't this mean that you have to address the specifics of each browser that might use your site though?<p>So if Konqueror 3.42 [made up version] has a bug giving a default of double the normal padding on h1 then I have to specifically check that this is addressed by the attempted normalization.<p>>"<i>Normalize.css is an alternative to CSS resets. The project is the product of 100′s of hours of extensive research by @necolas and @jon_neal on the differences between default browser styles.</i>"<p>Makes me think that I'm going to need to update every site using this with every new browser version that has a pixel difference in it's default style; a situation that a reset just works on.<p>Of course resets are subject to browser bugs too but it seems that they are more robust and more likely to just work ...?
> Normalize.css is modular<p>That is a strong claim given that the "modularisation" is realised adding banner comments in the CSS. I think it would had been better to have separate @import'ed files. Those worried about performance could use minificators while other, like me, could just use the parts they are interested in, in my case<p><pre><code> @import 'normalize.css/html5-fixes.css'
@import 'normalize.css/html5-defaults.css'</code></pre>
Is it just me or is hosting a single css file on a git repository a little silly? Not like one would continually check out the latest version.<p>That said, a reset file is always a good idea, and this is a nice evolution thereof.