Mayer's "I like to reimplement every style from scratch" turned into "You have to reimplement every style from scratch" (otherwise unspecified incompatibility bogeyman will bite you in vague ways).
Is "resetting" of font, applet and center really needed for new HTML5 pages?
Default styles are in the HTML5 spec. Actual stylesheets of all major browsers are available in their source repos or via introspection. For compatibility reasons there's really no need to reset everything "just in case". There are few specific styles which are annoyingly inconsistent. None of them are on kbd, u, strike, tfoot, label and dozen other elements that reset nukes.
I found that reset causes more trouble than it solves. Form elements don't react consistently to reset styles - it's better to keep browser's defaults.
WYSIWYG editors don't play nicely with reset (and sooner or later client might ask you for such editor).
And finally designers rarely bother to actually do what Mayer recommended for reset. They leave some styles reset to useless defaults, which makes it unnecessarily difficult to use pure semantic HTML later. Lack of outline is harmful to keyboard users.
For HTML5 reset it would be useful to set default styles for section, article, header and other elements that are unknown to HTML4 browsers. It doesn't do that...
I'm not really a fan of the underscore/dash naming scheme that they are using to keep the files on the top of the directory listing. Also, if you're going to do that, why have it be dash for the top level and underscore for the second levels?
God I hate resets.. Every time I see one of these I want to reach through my screen and slap the creator, then say go learn css before talking.
They make me, the developer, work so much harder, cause me so many more headaches, make my fingers type more, adds so much more code to the codebase, has all sorts of useless crap, and did I mention they make it harder on the developers?
regardless I took a look.
I downloaded the bare-bones one just to take a look around. 3 css files none more then 60 lines. using the always frowned upon @import command.
The _print css made me laugh. There is a main.css and a core.css. The core.css is empty and the main.css just says to import core.css. A lot of good thats gonna do.
I have no idea why a "HTML5" reset would have style sheets for IE5?
Horrible.. waste of time, to even use. Even worse because it has the nasty, awful meyerweb reset.
Hmm, something funky is happening when I zoom in or out using Chrome. Some of the fonts change font-family when zooming and then changes back to the correct font when the zooming animation is finished.
But surly the whole point of commenting on a post is to share our collective wisdom about whether or not code (or advice) is good.
The function of a HTML reset file is to ensure browsers on all systems behave the same way, but in this instance it appears to me that the author hasn't tested his own page on windows or perhaps just in Chrome, which would suggest that it might not good advice to use his reset file.
They did sort of say - let us know what's bad. It's a start, others will no doubt be doing their own bare template for HTML - I did my first proper HTML5 page yesterday, using JQuery too.
One thing I've just followed through is to merge my print styles (which tend to be minimal, turn off fancy images, remove some formatting) into my main CSS file - it was a Google page optimisation recommendation. I'm also using a reset based on YUI but without the non-standards IE hack; copy pasted to avoid a linked file as it's a single page "tool".
Is "resetting" of font, applet and center really needed for new HTML5 pages?
Default styles are in the HTML5 spec. Actual stylesheets of all major browsers are available in their source repos or via introspection. For compatibility reasons there's really no need to reset everything "just in case". There are few specific styles which are annoyingly inconsistent. None of them are on kbd, u, strike, tfoot, label and dozen other elements that reset nukes.
I found that reset causes more trouble than it solves. Form elements don't react consistently to reset styles - it's better to keep browser's defaults.
WYSIWYG editors don't play nicely with reset (and sooner or later client might ask you for such editor).
And finally designers rarely bother to actually do what Mayer recommended for reset. They leave some styles reset to useless defaults, which makes it unnecessarily difficult to use pure semantic HTML later. Lack of outline is harmful to keyboard users.
For HTML5 reset it would be useful to set default styles for section, article, header and other elements that are unknown to HTML4 browsers. It doesn't do that...