WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #14264, comment 21


Ignore:
Timestamp:
04/11/12 21:02:06 (2 years ago)
Author:
MarcusPope
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14264, comment 21

    initial v1  
    2020>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. 
    2121 
    22 ??? 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. 
     22??? 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.  Even worse is that the client side implementation is slightly different from the server side implementation so they don't always "correct" the html in the same way. 
    2323 
    24 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" 
     24Honestly I didn't see any reason to open a new bug when this ticket clearly and exactly outlined the use 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" 
    2525 
    2626I think this thread continues to outline difficulty in communicating with the core team.