261892 - {inc} doctype not parsed properly when page loaded REALLY slowly

Status: RESOLVED FIXED

(Core :: DOM: HTML Parser, defect)

Description

[Andrew Schultz]

with linux trunk build 2004092707, a DIV and nested TABLE are displayed with
100% height (of the window) if the page is loaded very slowly.  The TABLE has
100% height style, but the DIV does not, so the DIV and TABLE should be the
normal height for one line (except in quirks mode).  I serve up the testcase
with a PHP script that relays the file in chunks.  If the chunk size is 60 bytes
or less, the bug shows up.

I was unable to trigger the bug with document.body.offsetHeight.  Also, when the
bug shows up, a debug build prints the following 4 times (suggesting a parser bug?):
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(result)) failed, file nsHTMLTokens.cpp,
line 288
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(result)) failed, file nsHTMLTokenizer.cpp,
line 847

Comment 1

[Andrew Schultz]

Attachment: testcase

<div style="border: 1px solid red;">
    <table style="height: 100%" border="1">
      <tbody><tr><td>&nbsp;</td></tr></tbody>
    </table>
  </div>

Comment 2

[Martijn Wargers (dead)]

I can reproduce it 100% (at least, until now) with the clone slowly bookmarklet:
http://www.squarefree.com/bookmarklets/testbrowsers.html
Choose 1 character at a time, to reproduce the bug.

Comment 3

[Bernd]

wfm :-(, could you setup the testcase at some webserver? If this behaviour is
shown is the rendering mode really standards, or does the slowness trigger
quirks mode?
One could add some obvious quirk code to detect the quirks mode rendering.

Clone slowly removes the doctype so it creates a quirks mode document.

Comment 4

[Andrew Schultz]

a) yes, the doc is in quirks mode
b)
http://www.sens.buffalo.edu/~ajs42/slow.php?file=261892.html&chunk=1000&delay=100000
(look carefully at the first line)
c) The key seems to be that the doctype needs to be delivered in separate chunks

==> parser

Comment 5

[Uri Bernstein]

*** Bug 313895 has been marked as a duplicate of this bug. ***

Comment 6

[Uri Bernstein]

See also bug 268442 for a similar problem when using document.write().