[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:  closed
 Priority:  normal         |   Milestone:
Component:  TinyMCE        |     Version:  3.0
 Severity:  normal         |  Resolution:  maybelater
 Keywords:  HTML5 wpautop  |
---------------------------+-------------------------

Comment (by MarcusPope):

 @WraithKenny already pointed out where our impressions came from with
 regard to azzaoz so I'll just focus on the other half of his point:

 Replying to @azaozz:
 >This can be tested pretty easy/fast: make a webpage containing
 <a><h3>...</h3><p>...</p></a>, then look at the internal browser
 representation of the html.

 You are right, it is very easy to check that, so I did:
 http://www.marcuspope.com/img/block/block.html

 http://www.marcuspope.com/img/block/opera.png

 http://www.marcuspope.com/img/block/ff.png

 http://www.marcuspope.com/img/block/chrome.png

 http://www.marcuspope.com/img/block/ie.png

 As expected the browser properly constructs the document without any error
 correction or dom coercion.  These are internal representations of the
 document using their respective tools, not simply views of the downloaded
 source.  And they were compiled with the oldest versions of every browser
 I have installed.

 Replying to @azaozz:
 >You're right, however the original problem in this ticket has been fixed.
 TinyMCE supports article, section, aside, nav, hgroup, header, footer, and
 some other HTML 5 tags now so the ticket should be closed.

 ??? Again, I'm really confused because this ticket is "closed enhancement:
 maybelater."  Additionally the '''BUG''' is that when you switch from the
 HTML tab to the Visual tab in the edit screen it clobbers the HTML.  This
 has NOTHING to do with TinyMCE and EVERYTHING to do with the wpautop hook
 that wordpress binds to the tab switch event.  If you disable wpautop
 (both the client and server side implementations) and you try to reproduce
 this bug, you will find that TinyMCE doesn't clobber the HTML.

 Honestly I didn't see any reason to open a new bug when this ticket
 clearly and exactly outlined the test case and resulting problem.  And
 there was nothing in the responses that I, @CyberSkull, and others
 received that led me to believe my new bug ticket wouldn't be changed to a
 nice to have feature enhancement and closed for "maybelater"

 I think this thread continues to outline difficulty in communicating with
 the core team.

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