176910 - Text not rendering with noscript element not closed

Status: RESOLVED FIXED

(Core :: DOM: HTML Parser, defect)

Description

[Kjetil Kjernsmo]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020913 Debian/1.1-1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020913 Debian/1.1-1

Most of the stuff on the first page of http://www.bolignorge.no/ is not
rendered. The site has possibly some MS-specific code, but a discussion on the
list of EFF Norway indicated that it might have to be related to that table
elements are not closed. 

Reproducible: Always

Steps to Reproduce:
1. Just go to the above link
2.
3.

Actual Results:  
Text scrolling across the screen is displayed. A blue square is showed, but
nothing else.

Expected Results:  
Rendered the whole page.

This is obviously something for the quirk mode. The web page code is just very
bad, but probably just created thoughtlessly with Frontpage, so it is something
that might be seen elsewhere too.

The page was briefly discussed on the list of Electronic Frontier Norway, and
someone pointed out that the page rendered in ol' Netscape 4.74 if the table and
child elements had been closed. Thus, it may be something in the table layout
stuff. 

BTW, going OT now, I expressed in that discussion that web designers who do that
should be obsolete soon, and it turned out that the site is owned by an old
classmate of mine, with whom I've discussed that topic on a class reunion... :-)

Comment 1

[Boris Zbarsky [:bzbarsky]]

Attachment: minimal testcase

Doing any of the following fixes things:

1)  Fixing the broken </noscript> tag
2)  Putting <td> before the iframe.

Comment 2

[Boris Zbarsky [:bzbarsky]]

To parser.  Everything on the page below that point is dropped by the parser.

Since frontpage does not produce mismatched end tags like that (bad though it
may be, it is not that bad), I question the prevalence of markup like this...  

Comment 3

[John Keiser (jkeiser)]

This is fixed with the patch for bug 77296.

Comment 4

[John Keiser (jkeiser)]

Fixed with bug 77296.