"Compatibility tables for features in HTML5, CSS3, SVG and other upcoming web technologies."

How to make an background image scale without using a ton of JavaScript.

This may be worth looking into. I waffle on whether this sort of thing is ultimately a good decision — you're relying on someone else's framework, it takes a while to learn and master, and once you decide to go with it you're essentially stuck with it. But isn't that the case with any pseudo-framework developed for a website design? I should test this on a little project.

As seen on Normative.com.

Detailed to the point of being almost unreadable!

Ugly "Browse..." buttons be gone!

"The need for these distinctions becomes moot, of course, when no secondary actions are present. Make sure you really need each secondary action on a form and don’t add them indiscriminately."

It's about time. But when will this actually become an official recommendation? When universally adopted? And will that adoption be as awful as the previous implementations?

What works in which browsers.