Question from someone who is not an expert in crafting CSS: Is normalize.css something that needs to be actively maintained as newer (versions?) browsers come up or older browser have some changes ?<p>It sounds to me that CSS Reset might be a "bulldozer" and is absolutely inelegant, but I would not have to download a newer version of it every 6 months as I probably would have to do with normalize.css. Am I missing something here ?
Lots of good changes! I like the standard of prompting for installing Chrome Frame for IE6 users. Gives them the option of installing the Chrome Frame or still getting to the content!<p>And very interested to try out normalize.css...
They seem to have pulled down the Mobile boilerplate, which is too bad - I was a fan of that.<p>I wonder if they're implying we should use html5 v2 for mobile now. I know v2 has a "mobile-first" focus...
My first thought when reading this was that maybe my HTML5 boilerplate is too plain. See, mine looks like this:<p><pre><code> <!DOCTYPE html>
</code></pre>
Maybe that's too small, but I could have sworn that a big point in HTML5 was that HTML could be a lot looser and have <i>less</i> boilerplate, not more.