13354 - Content ignored because of unclosed <P> inside <IFRAME>

Status: VERIFIED DUPLICATE of bug 22842

(Core :: DOM: HTML Parser, defect, P2)

Description

[David :Bienvenu]

This web page doesn't load with the 5.0 browser, except for the ad. I tried it
with 4.6 and it loaded fine.

here's what got dumped to the console:

Recieving ... datais=CTFTW; path=/; domain=.datais.com

Recieving ... datref=(null)
freq52=1|936818398; expires=Thursday, 9-Sep-1999 16:19:58 GMT
ryanstev_1=52-1; path=/; domain=.datais.com
dataisUN=a1d5nm4ld9; expires=Thursday, 7-Sep-2000 15:19:58 GMT; path=/

Recieving ... datref=(null)
ryanstev_1=48-2; path=/; domain=.datais.com
Going to reload
Error loading URL http://www.kaitaia.com/top.htm
Document: Done (0.078 secs)
Error loading URL http://leader.linkexchange.com/1/X1123330/clickto_X1084922?262
,47
Document: Done (3.531 secs)

Comment 1

[David :Bienvenu]

The console messages may be a red herring - the page failed to load with no
status messages the second time I tried.

Comment 2

[Mats Palmgren (inactive)]

Attachment: testcase, distilled from www.realcountrymm.com

Comment 3

[Mats Palmgren (inactive)]

There is an unclosed <P> inside the <IFRAME> causing the rest of the
page to be considered as <IFRAME> content and thus (correctly) ignored.
However the 4.x browsers seems to do the right thing and close the <P>
upon seeing </IFRAME>.

Comment 4

[leger]

Resetting QA contact from leger.

Comment 5

[rickg]

Harish -- the test case seems to show that the document is coming in well
formed. Then when the source for the iframe comes in the document gets
constructed wrong. This is likely a sink problem.

Comment 6

[ekrock's old account (dead)]

Bulk moving [testcase] code to new testcase keyword. Sorry for the spam!

Comment 7

[harishd]

Moving to M16.

Comment 8

[harishd]

Not a beta blocker. Moving to M17

Comment 9

[harishd]

Marking it for future.

Comment 10

[Hixie (not reading bugmail)]

This is a serious error!!! The markup snippet is valid -- we should NOT BE
breaking on this!!

We need to fix this to support HTML4. Nominating nsbeta3. This is more important
to fix than most compat issues...

Comment 11

[Nisheeth Ranjan]

Removed nsbeta3 nomination from futured bugs.

Comment 12

[Nisheeth Ranjan]

Should not remove nsbeta3 nomination. Thanks to dbaron and ekrock for the heads
up. Re-adding the nomination and marking nsbeta3-.

Comment 13

[rickg]

This is very bad! Fortunately, it's a dup of bug 22842, which is fixed in my 
tree.

Comment 14

[rickg]

*** This bug has been marked as a duplicate of 22842 ***

Comment 15

[Keyser Sose]

Duplicate which is resolved anyway. Marking as verified.