3 ms·
I use Richard Clark's CSS Reset paired with my custom-built scaffolding CSS stylesheet. It rips out all the base styles applied by browsers, and builds them bac
by Pewpewarrows 16y ago
I use Richard Clark's CSS Reset paired with my custom-built scaffolding CSS stylesheet. It rips out all the base styles applied by browsers, and builds them back up so that absolutely everything: fonts, form elements, tables, code blocks, etc not only all look identical in every browser, but are easy on the eyes.
I find it pretty laughable that developers ignore Resets because of a little extra noise in their CSS debuggers. That's like advocating against using a framework for another language because your stack traces are a little longer by default. In Chrome's Dev Tools you can hover over any final computed style to determine exactly what file and line it came from, and the rules are shown most-specific first. I rarely if ever have to scroll down to the broader rules where the duplicated Reset noise tends to be more prominent. I haven't used Firebug in a year or two, but I'm assuming it has similar developer-friendly functionality.
- lukeschlather 16y agoIt seems more like those who categorically argue you should avoid frameworks, because hand-crafted code is going to be faster. Which is about the only concrete benefit I see to avoiding resets. I'm probably going to tweak about the same number of properties, and the defaults are saner.