What ciaobello told you is, that if you debug your css with f.e. firebug, there is no chance to not see all CSS that arrived at the browser and is responsible for rendering the page.
normalize.css is not a real css reset it just tries to fix some problems.
Personaly I don't like the Contao css reset as there are things like
HTML Code:
body,div,h1,h2,h3,h4,h5,h6,p,blockquote,pre,code,ol,ul,li,dl,dt,dd,figure,table,th,td,form,fieldset,legend,input,textarea {
margin:0;
padding:0;
}
which can be done by
HTML Code:
* {
margin: 0;
padding: 0;
}
Or
HTML Code:
ul {
list-style-type:none;
}
while it is not comfortable to have no list points on list. They're only unwanted in navigations, where you can remove them.
Or
HTML Code:
font:12px/1 "Lucida Grande","Lucida Sans Unicode",Verdana,sans-serif;
where I prefer
HTML Code:
font-family: "Lucida Grande","Lucida Sans Unicode",Verdana,sans-serif;
font-size: 1rem;
line-height: 1;
And there is no space behind a colon in contao css files.
I also don't like css resets where every element has
HTML Code:
*:before {
blabla...
}
And I don't like javascript modernizer which puts 43 modernizer classes in the BODY-Tag.
This all makes debugging css more difficult.
Take a look at different css frameworks like YAML, Bootstrap, Foundation and others to learn from their reset (maybe they are not better than contaos reset but you can compare their approach).
Train your css debugging skills.
Bookmarks