[wp-trac] [WordPress Trac] #14264: Add support for HTML5 Section elements to editor

[WordPress Trac]

#14264: Add support for HTML5 Section elements to editor
-------------------------+------------------------------
 Reporter:  cyberskull   |       Owner:
     Type:  enhancement  |      Status:  reopened
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  TinyMCE      |     Version:  3.0
 Severity:  normal       |  Resolution:
 Keywords:  HTML5        |
-------------------------+------------------------------

Comment (by MarcusPope):

 C'mon Azaozz, partially work?  http://html5boilerplate.com/  this stuff is
 solid, and has been around for a couple years now.

 And no, I'm not suggesting that we force all installations to use it, but
 that doesn't mean we should leave code in the system that prevents their
 usage in a plugin.  Even better make it an option in the admin.  Only the
 latest browsers are supported for the admin area anyway, and they all
 support HTML5 now.

 HTML5 style Block Level Anchor tags have actually been supported for years
 (10+) now.  They weren't considered valid markup by xhtml standards, but
 browsers knew what to do with them.  I'm pretty sure even IE3.0 supported
 them, but my memory is fading these days.

 But this is NOT a TinyMCE issue.  TinyMCE actually supports them
 completely (except for around tables of course, but then again I don't
 think any browser supports that yet.)  I am sure about the support in
 contentEditable mode because I developed a solution for it.  You even said
 yourself tinyMCE supports all HTML5 tags.

 Mostly I was opening this ticket because of your comment: "Closing as
 wontfix for now. I'm sure we will enable HTML 5.0 support by default when
 it becomes possible."  Well, now it would be possible via a plugin if it
 were not for some broken (ok outdated) logic in WPAUTOP.

 And the only reason I suggested enhancing the allowable_children option in
 the core config options is because WP has already added other html5 tags
 to the core config for tinyMCE in the changeset I referenced above.  It
 wouldn't impact editing of xhtml content unless someone actually used the
 construct (ie wrapped an anchor around a block element.)

 But if you do that today, and you save or switch tabs the markup is
 completely mangled because wpautop mucks it up.

 I don't really care either way, I have managed to disable wpautop for my
 own projects and my life is much happier as a result.  But I figured for
 those who enjoy the use of wpautop formatting, they might also enjoy block
 level anchor tags if their theme supported html5 too.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/14264#comment:9>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software