Hacker News new | past | comments | ask | show | jobs | submit login

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...




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: