4 ms·
I've landed solidly in "always reset" territory. There are just so many inconsistencies between browsers/platforms that I'd rather have everything looking as co
by cheald 16y ago
I've landed solidly in "always reset" territory. There are just so many inconsistencies between browsers/platforms that I'd rather have everything looking as consistent as possible, and work from there. It does add extra garbage to Firebug, but it's worth not having to debug a display issue on a browser on a platform that I don't have access to.
- pornel 16y agoBrowser stylesheets are well-known, default styles testable, and yet most resets still nuke everything "just in case". http://css-class.com/test/css/defaults/UA-style-sheet-defaults.htm http://css-class.com/test/css/defaults/UA-style-sheet-defaul... There are only few differences that could break layout. Hard problems are caused by different interpretation of applied styles, not because of defaults. In case of form elements (which are underspecified in CSS), touching their style can make inconsistencies worse (different browsers use different box model for form elements, and achieve similar size with browser-specific defaults).
- nitrogen 16y agoMy biggest gripe with form elements is when sites (and browsers) expect the default to be black text on a white background, and change the foreground text to a near-black color. This wreaks havoc on systems with a dark colorscheme, where system input boxes have white text on a black background. This is the sole reason why I no longer use light-on-dark colorschemes, which I find much more pleasing, on my desktop (and laptop).