Closed
Bug 469769
Opened 16 years ago
Closed 16 years ago
"ASSERTION: Too many calls to ScriptDidExecute" with document.write in deferred script
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: assertion, testcase)
Attachments
(1 file)
|
(deleted),
text/html
|
Details |
Loading the testcase triggers:
###!!! ASSERTION: Too many calls to ScriptDidExecute: 'mScriptsExecuting > 0', file /Users/jruderman/central/parser/htmlparser/src/nsParser.cpp, line 1810
The assertion was added in bug 444322, and <script defer> was added in bug 28293.
Bug 461555 will change the behavior of this testcase. (In fact, the testcases for that bug also trigger this assertion.) Will bug 461555 fix this bug?
Blocks: 28293
|
||
Comment 1•16 years ago
|
||
Yes, this happens because when we start processing deffered scripts, there is no parser; then the document.write() causes a parser to be created and that parser only ever sees the ScriptDidExecute call.
When bug 461555 lands, the original parser will still be alive when we execute deferred scripts.
Depends on: 461555
|
Reporter | |
Comment 2•16 years ago
|
||
WFM. I'm guessing this was fixed by bug 461555 or bug 483818.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Yeah, those two together fixes this. In two ways.
Depends on: 483818
Resolution: WORKSFORME → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•