Doesn't this mean that you have to address the specifics of each browser that might use your site though?
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.
>"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."
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.
Of course resets are subject to browser bugs too but it seems that they are more robust and more likely to just work ...?
Not really. The outcome with normalize.css is as splendid as with the reset bull-doze approach. The advantage of normalize however, is that size of your stylesheet is much smaller.
And probably you'll be more aware about vendor treatment of different properties. Unlike with include-and-forget (lazy-bum) approach of reset.
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.
>"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."
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.
Of course resets are subject to browser bugs too but it seems that they are more robust and more likely to just work ...?