Closed
Bug 564098
Opened 15 years ago
Closed 13 years ago
[HTML5] "ASSERTION: Script global object not ready"
Categories
(Core :: DOM: Navigation, defect)
Core
DOM: Navigation
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jruderman, Unassigned)
Details
(Keywords: assertion, testcase)
Attachments
(1 file)
243 bytes,
text/html
|
Details |
dom/base/crashtests/504224.html triggers:
###!!! ASSERTION: Script global object not ready: 'GetDocument()->GetScriptGlobalObject()', file /home/jruderman/mozilla-central/parser/html/nsHtml5TreeOpExecutor.h, line 144
Flags: in-testsuite+
Updated•15 years ago
|
Priority: -- → P2
Comment 1•15 years ago
|
||
The data: URL document never gets its script global object set to a non-null value. (But why?)
Is
var src=document.getElementById('src');
intentional in the test case. There seems to be no element with id 'src'.
Updated•15 years ago
|
OS: Linux → All
Hardware: x86_64 → All
Comment 2•15 years ago
|
||
Note: Manually reloading does not trigger this. Reloading from script is needed, curiously.
Assignee: nobody → hsivonen
Status: NEW → ASSIGNED
Comment 3•15 years ago
|
||
Things start going wrong, because
FindContainerView() at
http://mxr-test.konigsberg.mozilla.org/mozilla-central/source/layout/base/nsDocumentViewer.cpp#850
returns null, which seems to lead to the script global object of the document not getting set to an inner window object.
Is this expected (and the assertion in the HTML5 parser wrong)? Or is it wrong that a parse can start on a document whose window (iframe) has been detached? It seems kinda scary for the parser to parse into a document (with scripting enabled and all) without the document having an inner window object associated with it.
![]() |
||
Comment 4•15 years ago
|
||
Hmm. It seems odd that we manage to parse for a document that's detached, yes.... Did that not use to happen with the old parser here?
Comment 5•15 years ago
|
||
(In reply to comment #4)
> Hmm. It seems odd that we manage to parse for a document that's detached,
> yes.... Did that not use to happen with the old parser here?
It happens with the old parser, too. We just don't have an assert in the old parser in the tree.
Based on that, moving this out of the Parser component to Document Navigation.
Assignee: hsivonen → nobody
Component: HTML: Parser → Document Navigation
Priority: P2 → --
QA Contact: parser → docshell
Comment 6•15 years ago
|
||
See also the #whatwg IRC log from
http://krijnhoetmer.nl/irc-logs/whatwg/20100720#l-624
to about the end of that day's log.
Reporter | ||
Comment 7•14 years ago
|
||
Still happens after a recent change to the assertion (in bug 651072).
###!!! ASSERTION: Script global object not ready: '!mDocShell || GetDocument()->GetScriptGlobalObject()', file /builds/slave/m-cen-osx64-dbg/build/parser/html/nsHtml5TreeOpExecutor.h, line 157
Reporter | ||
Comment 8•13 years ago
|
||
WFM. Maybe fixed by bug 717488?
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•