WordPress Trac: Ticket #16436: Use <article> in theme markuphttps://core.trac.wordpress.org/ticket/16436
<p>
More here.
<a class="ext-link" href="http://html5doctor.com/the-article-element/"><span class="icon">​</span>http://html5doctor.com/the-article-element/</a> and
<a class="ext-link" href="http://dev.w3.org/html5/spec/Overview.html#the-article-element"><span class="icon">​</span>http://dev.w3.org/html5/spec/Overview.html#the-article-element</a>
</p>
<p>
If we are already using it, than sorry.
</p>
en-usWordPress Trachttps://core.trac.wordpress.org/chrome/site/your_project_logo.pnghttps://core.trac.wordpress.org/ticket/16436
Trac 1.0.1ericmannTue, 01 Feb 2011 17:29:28 GMTstatus changed; resolution sethttps://core.trac.wordpress.org/ticket/16436#comment:1
https://core.trac.wordpress.org/ticket/16436#comment:1
<ul>
<li><strong>status</strong>
changed from <em>new</em> to <em>closed</em>
</li>
<li><strong>resolution</strong>
set to <em>invalid</em>
</li>
</ul>
<p>
Markup of pages sent to the front-end is a theme issue, not a core issue. The same goes for the child elements of <tt>&lt;article&gt;</tt>.
</p>
TicketscribuTue, 01 Feb 2011 17:32:40 GMTstatus, type, component, summary changed; keywords, resolution deletedhttps://core.trac.wordpress.org/ticket/16436#comment:2
https://core.trac.wordpress.org/ticket/16436#comment:2
<ul>
<li><strong>status</strong>
changed from <em>closed</em> to <em>reopened</em>
</li>
<li><strong>type</strong>
changed from <em>feature request</em> to <em>enhancement</em>
</li>
<li><strong>component</strong>
changed from <em>Post Types</em> to <em>Themes</em>
</li>
<li><strong>summary</strong>
changed from <em>[HTML5] use <article> in the post.</em> to <em>Use <article> in theme markup</em>
</li>
<li><strong>keywords</strong>
<em>3.2</em> removed
</li>
<li><strong>resolution</strong>
<em>invalid</em> deleted
</li>
</ul>
<p>
Yes, but we bundle the Twentyten theme with Core.
</p>
TicketMalcjohnTue, 01 Feb 2011 19:19:15 GMThttps://core.trac.wordpress.org/ticket/16436#comment:3
https://core.trac.wordpress.org/ticket/16436#comment:3
<p>
Hi,
i thought it should be made in the core. It has nothing to do with a theme. Doesn't matter what theme is istalled, because you are sending the post from the editor (Ty..) and it shows on the theme.
</p>
<p>
BTW sorry for my poor English.
</p>
TicketandrewrynoWed, 02 Feb 2011 04:30:49 GMThttps://core.trac.wordpress.org/ticket/16436#comment:4
https://core.trac.wordpress.org/ticket/16436#comment:4
<p>
It's still a theme issue because the themes only take the content and wrap it in whatever HTML the theme developer wants. However since twentyten is pushed with core, it can probably be changed with that theme.
</p>
<p>
If we are changing to use &lt;article&gt; in twentyten, would it make sense to just implement &lt;header&gt;, &lt;section&gt;, etc. as well? I would vote for sticking as is since IE doesn't support all of the new elements well enough for the change.
</p>
TicketsolarissmokeWed, 02 Feb 2011 05:18:36 GMThttps://core.trac.wordpress.org/ticket/16436#comment:5
https://core.trac.wordpress.org/ticket/16436#comment:5
<p>
Javascript DOM manipulation in IE&lt;8 is a disaster when you use these new HTML5 elements - basic things like <tt>innerHTML</tt> calls and <tt>getElementsByTagName</tt> don't work properly because it doesn't recognise the new elements as valid - and for that reason I don't think core is ready for these new elements.
</p>
<p>
Suggest wontfix/maybelater - at least until IE loses majority market share ;)
</p>
TicketericmannWed, 02 Feb 2011 05:20:15 GMThttps://core.trac.wordpress.org/ticket/16436#comment:6
https://core.trac.wordpress.org/ticket/16436#comment:6
<p>
Replying to <a class="closed" href="https://core.trac.wordpress.org/ticket/16436#comment:4" title="Comment 4 for Ticket #16436">andrewryno</a>:
</p>
<blockquote class="citation">
<p>
It's still a theme issue because the themes only take the content and wrap it in whatever HTML the theme developer wants.
</p>
</blockquote>
<p>
Exactly my point. If you want WordPress to put out HTML5, that's up to the theme you're using. If you want it to render XHTML instead, that's also up to the theme. It's a decision made not by core, but by the designer/coder of your front-end.
</p>
<blockquote class="citation">
<p>
I would vote for sticking as is since IE doesn't support all of the new elements well enough for the change.
</p>
</blockquote>
<p>
The biggest advantage of using WordPress over other systems has always been compatibility. As Matt said once at a WordCamp, you can take pretty much any well-put-together theme from 2.0 and drop it on a 3.0 (or 3.1) installation and it will still work. We don't break things for people using older systems - for a bundled theme, we should take the same approach.
</p>
<p>
While HTML5 is all shiny, new, and cool ... IE doesn't properly support it, and IE is still the market leader. I'm a big proponent of "decisions, not options" so while having the *option* to use HTML5 for TwentyTen would be nice, I think we should keep things as-is and leave that specific option available for a child theme.
</p>
<p>
And building a TwentyTen child theme that uses <tt>&lt;article&gt;</tt> and <tt>&lt;header&gt;</tt> and <tt>&lt;footer&gt;</tt> isn't too difficult.
</p>
TicketMalcjohnWed, 02 Feb 2011 19:10:44 GMTkeywords sethttps://core.trac.wordpress.org/ticket/16436#comment:7
https://core.trac.wordpress.org/ticket/16436#comment:7
<ul>
<li><strong>keywords</strong>
<em>3.2</em> <em>twentyten</em> added
</li>
</ul>
<p>
OK, thanks for feetback. set for the future release of twentyten.
</p>
TicketnacinWed, 02 Feb 2011 19:18:37 GMTstatus changed; resolution set; keywords, milestone deletedhttps://core.trac.wordpress.org/ticket/16436#comment:8
https://core.trac.wordpress.org/ticket/16436#comment:8
<ul>
<li><strong>keywords</strong>
<em>3.2</em> <em>twentyten</em> removed
</li>
<li><strong>status</strong>
changed from <em>reopened</em> to <em>closed</em>
</li>
<li><strong>resolution</strong>
set to <em>maybelater</em>
</li>
<li><strong>milestone</strong>
<em>Awaiting Review</em> deleted
</li>
</ul>
<p>
Going to close as maybelater, as Twenty Eleven will be HTML5. Don't need this ticket to remind the initial developers :-)
</p>
TicketMalcjohnWed, 23 Feb 2011 20:20:50 GMTstatus changed; keywords set; resolution deletedhttps://core.trac.wordpress.org/ticket/16436#comment:9
https://core.trac.wordpress.org/ticket/16436#comment:9
<ul>
<li><strong>keywords</strong>
<em>reporter-feedback</em> added
</li>
<li><strong>status</strong>
changed from <em>closed</em> to <em>reopened</em>
</li>
<li><strong>resolution</strong>
<em>maybelater</em> deleted
</li>
</ul>
<p>
This article from yeasterday is great. Below is a link to download it. Maybe we should use it as our standart theme, which we can use instead of ours.
</p>
<p>
Links:
<a class="ext-link" href="http://www.smashingmagazine.com/2011/02/22/using-html5-to-transform-wordpress-twentyten-theme/"><span class="icon">​</span>http://www.smashingmagazine.com/2011/02/22/using-html5-to-transform-wordpress-twentyten-theme/</a>
<a class="ext-link" href="http://www.twentytenfive.com/"><span class="icon">​</span>http://www.twentytenfive.com/</a>
</p>
TicketnacinWed, 23 Feb 2011 20:22:57 GMThttps://core.trac.wordpress.org/ticket/16436#comment:10
https://core.trac.wordpress.org/ticket/16436#comment:10
<p>
Indeed, nice article. My original point stands: Twenty Eleven will be HTML5.
</p>
TicketnacinWed, 23 Feb 2011 20:23:16 GMTstatus changed; resolution sethttps://core.trac.wordpress.org/ticket/16436#comment:11
https://core.trac.wordpress.org/ticket/16436#comment:11
<ul>
<li><strong>status</strong>
changed from <em>reopened</em> to <em>closed</em>
</li>
<li><strong>resolution</strong>
set to <em>maybelater</em>
</li>
</ul>
Ticketocean90Sat, 21 May 2011 18:40:36 GMTstatus changed; keywords, resolution deletedhttps://core.trac.wordpress.org/ticket/16436#comment:12
https://core.trac.wordpress.org/ticket/16436#comment:12
<ul>
<li><strong>keywords</strong>
<em>reporter-feedback</em> removed
</li>
<li><strong>status</strong>
changed from <em>closed</em> to <em>reopened</em>
</li>
<li><strong>resolution</strong>
<em>maybelater</em> deleted
</li>
</ul>
Ticketocean90Sat, 21 May 2011 18:41:12 GMTstatus changed; resolution sethttps://core.trac.wordpress.org/ticket/16436#comment:13
https://core.trac.wordpress.org/ticket/16436#comment:13
<ul>
<li><strong>status</strong>
changed from <em>reopened</em> to <em>closed</em>
</li>
<li><strong>resolution</strong>
set to <em>duplicate</em>
</li>
</ul>
<p>
<a class="closed ticket" href="https://core.trac.wordpress.org/ticket/17198" title="task (blessed): New theme for 3.next -- Twenty Eleven (closed: fixed)">#17198</a>
</p>
Ticket