[wp-trac] [WordPress Trac] #15918: WP adding tags no matter what the settings are

WordPress Trac wp-trac at lists.automattic.com
Mon Dec 20 16:17:39 UTC 2010


#15918: WP adding tags no matter what the settings are
--------------------------+------------------------------
 Reporter:  retrib        |       Owner:  dunno
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Formatting    |     Version:  3.0.3
 Severity:  major         |  Resolution:
 Keywords:  html5         |
--------------------------+------------------------------
Changes (by scribu):

 * keywords:  html5, theme parser => html5
 * component:  Template => Formatting


Old description:

> Hi guys! I've got latest WP installation (3.0.3) and found strange bug in
> posts parser.
>
> Create article with following HTML:
> <div class="wassup"><a href="#">WP IZ ASSUM</a></div>
> Browser will get: <div class="wassup"><a href="#">WP IZ ASSUM</a></div>
> All seems to be fine! Now get rid of unnecessary div.
>
> Create article with following HTML:
> <a href="#">WP IZ ASSUM</a>
> Browser will get: <p><a href="#">WP IZ ASSUM</a></p>
> Dunno why there is extra <p> but who cares. All seems to be OK.
>
> Create article with following HTML:
> <figure><a href="#">WP IZ ASSUM</a>
> </figure>
> Browser will get:
> <figure><a href="#">WP IZ ASSUM</a><br />
> </figure>
>
> Now isn't that cool? But check what is even cooler!
>
> Create article with following HTML:
> <figure><a href="#">WP IZ ASSUM</a>
> <figcaption>NO IT'S BUGGY AS HELL</figcaption>
> </figure>
>
> Browser will get:
> <figure><a href="#">WP IZ ASSUM</a></p>
> <figcaption>NO IT’S BUGGY AS HELL</figcaption>
> </figure>
>
> Wow! Say hello to invalid markup and rendering problems! Auto-closing of
> tags turned off. No matter of the settings I still get this nice messed
> up html. WYSIWYG turned off also.

New description:

 Hi guys! I've got latest WP installation (3.0.3) and found strange bug in
 posts parser.

 Create article with following HTML:

 {{{
 <div class="wassup"><a href="#">WP IZ ASSUM</a></div>
 }}}

 Browser will get:

 {{{
 <div class="wassup"><a href="#">WP IZ ASSUM</a></div>
 }}}

 All seems to be fine! Now get rid of unnecessary div.

 Create article with following HTML:

 {{{
 <a href="#">WP IZ ASSUM</a>
 }}}

 Browser will get:

 {{{
 <p><a href="#">WP IZ ASSUM</a></p>
 }}}

 Dunno why there is extra <p> but who cares. All seems to be OK.

 Create article with following HTML:

 {{{
 <figure><a href="#">WP IZ ASSUM</a>
 </figure>
 }}}

 Browser will get:

 {{{
 <figure><a href="#">WP IZ ASSUM</a><br />
 </figure>
 }}}

 Now isn't that cool? But check what is even cooler!

 Create article with following HTML:

 {{{
 <figure><a href="#">WP IZ ASSUM</a>
 <figcaption>NO IT'S BUGGY AS HELL</figcaption>
 </figure>
 }}}

 Browser will get:
 {{{
 <figure><a href="#">WP IZ ASSUM</a></p>
 <figcaption>NO IT’S BUGGY AS HELL</figcaption>
 </figure>
 }}}

 Wow! Say hello to invalid markup and rendering problems! Auto-closing of
 tags turned off. No matter of the settings I still get this nice messed up
 html. WYSIWYG turned off also.

--

Comment:

 The problem is that wpautop() doesn't know how to treat the new HTML5 tags
 yet.

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


More information about the wp-trac mailing list