147566 - Concurrent invalid tags (P and B) outside CAPTION causing remaining text to become bold

Status: RESOLVED FIXED

(Core :: DOM: HTML Parser, defect)

Description

[石庭豐 (Seak, Teng-Fong)]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3)
Gecko/20020523
BuildID:    20020523

In this web page, the text becomes bold from the paragraph starting at "In
addition, because".  I've looked in the page source but didn't see any unclosed
<b> tag. I note that in the table before that paragraph, the author had used
twice <b> but they are closed.  He also used <p> within <caption> but normally
<p> in this case is ignored.

So, probably a bug in Mozilla.

Reproducible: Always

Comment 1

[Daniel Bratell]

That part of the page looks like:

<p>
<b>
<caption>
<center><b>Table 2. Old document object vs. new document
and body objects</b></center></caption>
</b>
</p>

<tr>

Comment 2

[石庭豐 (Seak, Teng-Fong)]

Oops, I made a mistake.  The <p> tag is within _<table>_ , not <caption> tag. 
By any way, <p> isn't allowed within <table> and it should be ignored.

Comment 3

[Boris Zbarsky [:bzbarsky]]

To parser

Comment 4

[石庭豐 (Seak, Teng-Fong)]

Attachment: Reduced test case

Comment 5

[石庭豐 (Seak, Teng-Fong)]

I've reduced the webpage to a minimum test case.

The problem comes from the fact that the author wrongly used <p> within <table>
and outside <caption>, and then he wrongly (again!) used <b> between <p> and
<caption> (cf the comments inside the HTML file).  Strangely, the effect of <b>
doesn't stop at </b> after </caption> nor at </p>.  But since "The CAPTION
element is only permitted immediately after the TABLE start tag", cf.
http://www.w3.org/TR/html4/struct/tables.html#h-11.2.2

or on the other hand, <p> isn't allowed immediately inside <table>, <p> must be
ignored.

Comment 6

[Blake Kaplan (:mrbkap) (inactive)]

Taking, there might be a possible fix.

Comment 7

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

I believe this is fixed by bug 487949.

Comment 8

[石庭豐 (Seak, Teng-Fong)]

I'm using FF 3.5.1 but the bug is still there.  Let's wait until the fix of 487949 gets into the main trunk first and we'll see.