Make WordPress Core

Opened 18 years ago

Closed 15 years ago

Last modified 15 years ago

#7009 closed defect (bug) (invalid)

Invalid XHTML Produced by Comments

Reported by: singpolyma Owned by:
Priority: normal Milestone:
Component: Formatting Version: 2.7
Severity: normal Keywords:
Cc: Focuses:

Description

If you look at ​http://singpolyma.net/plugins/actionstream/#comment-67645 you will see that a <p> tag is opening before a <code> tag - and then closing *inside* the <code> tag - clearly in violation of XHTML (or even HTML4) specs. There is a similar problem near the </code>. These <p> blocks are being generated by WordPress (the <code> tags were entered by the user), so it seems to be a bug.

Change History (11)

#1 @DD32
18 years ago

  • Milestone → 2.6
  • Version → 2.5

#2 @mrmist
18 years ago

  • Keywords needs-patch added
  • Milestone 2.9 → 2.8
  • Priority high → normal
  • Severity major → normal
  • Version 2.5 → 2.7

Still reproducable.

#3 @ryan
17 years ago

  • Component General → Comments
  • Owner anonymous removed

#4 @Denis-de-Bernardy
17 years ago

  • Milestone 2.8 → Future Release

#5 @Denis-de-Bernardy
17 years ago

there is a balanceTags call on pre_comment_content. shouldn't this deal with it, or is it really a balanceTags bug?

#6 @Denis-de-Bernardy
17 years ago

  • Component Comments → Formatting
  • Milestone Future Release → 2.9

#7 @dwright
17 years ago

  • Cc david_v_wright@… added

I can not reproduce this issue.

how did you reproduce this issue?

the site in question appears fine to me.

<p><code><br>
Warning: simplexml_load_string() [function.simplexml-load-string]: Entity: line 1: parser error : Start tag expected, '&lt;' not found in /var/www/vhosts/dev.boldlygoing.com/httpdocs/wp-content/plugins/wp-diso-actionstream/actionstream.php on line 323</code></p>

#8 @ryan
17 years ago

  • Milestone 2.9 → Future Release

#9 @solarissmoke
16 years ago

  • Keywords close added; needs-patch removed

Can't reproduce - and the HTML in the link provided looks fine as dwright says.

#10 @solarissmoke
15 years ago

  • Keywords close removed
  • Resolution → invalid
  • Status new → closed

No feedback on how to reproduce.

#11 @ocean90
15 years ago

  • Milestone Future Release
Note: See TracTickets for help on using tickets.