Closed
Bug 568470
Opened 14 years ago
Closed 14 years ago
[HTML5] A page with a sleep() in the script generating it shows no data until after the sleep ends
Categories
(Core :: DOM: HTML Parser, defect, P2)
Tracking
()
RESOLVED
FIXED
People
(Reporter: bzbarsky, Assigned: hsivonen)
References
()
Details
Attachments
(3 files)
4.72 KB,
text/html
|
Details | |
5.42 KB,
patch
|
mozilla+ben
:
review+
|
Details | Diff | Splinter Review |
2.42 KB,
patch
|
Details | Diff | Splinter Review |
I'm pointing to a url that shows the bug, but since that might go away, also attaching the page in question. See the "sleep() call goes here" comment in the attachment for where the sleep() should be in the script on the server. In this case we should render the content before the sleep() ends.
Assignee | ||
Comment 1•14 years ago
|
||
Writing the test case for this was pretty annoying... Still need to check that the timing don't go orange on the tinderbox.
Assignee | ||
Updated•14 years ago
|
Attachment #447946 -
Flags: review?(mozilla+ben)
Assignee | ||
Updated•14 years ago
|
Priority: -- → P2
Comment 2•14 years ago
|
||
These changes make the iframe call parent.parsed() directly instead of requiring the parent to poll the iframe's DOM using setInterval. If this seems like a reasonable change, you could play with the timings to make the test shorter, but IMO it's short enough already. r=me with the changes I suggested, or an explanation of why they're invalid.
Comment 3•14 years ago
|
||
Comment on attachment 447946 [details] [diff] [review] Flush tree ops more eagerly when stopping speculation r=me given what I said in comment 2.
Attachment #447946 -
Flags: review?(mozilla+ben) → review+
Assignee | ||
Comment 4•14 years ago
|
||
Thanks. The suggested changes to the test invalidate the test, because the added </script> tag flushes the tree ops unconditionally and the test is trying to test if the ops get flushed without a </script> or EOF forcing a flush.
Assignee | ||
Comment 5•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/6060488c2971
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•14 years ago
|
||
The test case when perma-orange on Linux tinderboxen, so I first tried to adjust the timings http://hg.mozilla.org/mozilla-central/rev/a9501fcd9c25 and then disabled the test http://hg.mozilla.org/mozilla-central/rev/0e0e2516f04e It seems this one is hard to test reliably. :-(
Flags: in-testsuite?
You need to log in
before you can comment on or make changes to this bug.
Description
•