The theme now passes validation as HTML5. The calendar widget and gallery shortcode generate HTML that do not validate and should be addressed in core — but a default install will now validate. (Updated, see comments.)
The theme now passes validation as HTML5. The calendar widget and gallery shortcode generate HTML that do not validate and should be addressed in core — but a default install will now validate. (Updated, see comments.)
Twenty Ten 
I’ve submitted a patch that removes the offending attributes from the calendar widget. There may be a better approach, but I wanted to mention it to the core developers. You can track it here: http://core.trac.wordpress.org/ticket/11554
And I’ve customized the output of the gallery shortcode to remove the inline CSS it generates by default. 2010 galleries now validate. đŸ™‚
So 2010 will be in HTML5 right? This is what I can deduce from the source code. That is cool!
That is correct. Others will have the final say on what goes into WordPress core, of course, but 2010 was designed with HTML5 in mind.
That’s awesome in my opinion. I envision WP themes shifting to HTML5 little by little.
whats HTML5 on that code? i neither see any <header> nor <nav> nor <aside> nor any nor <article> elements. just that it validates, does not make it HTML5.
Actually, that’s exactly what makes it HTML5. đŸ™‚ It’s got a valid doctype and it’s valid code — that’s all it needs. The elements you mention are great additions to HTML that make it more semantic, but their use (or lack thereof) doesn’t make or break the markup.
ok you’re right on the valid code. but all you got is an xhtml 1.0 strict page that lacks the long doctype line.
wouldn’t it be fantastic to keep up with the progress and have a fully semantic yet downward compatible standard theme in the all new cutting edge wordpress 3.0?
Neither does , , or elements on the markup make it HTML5 if it has, let’s say, an XHTML document specification. The 2010 needs to get us into HTML5 – the duty to push things to the edge is to the community.