Closed Bug 319713 Opened 19 years ago Closed 19 years ago

document.close handled from an external script, is mildly incorrect

Categories

(Core :: DOM: Core & HTML, defect)

x86
Linux
defect
Not set
minor

Tracking

()

RESOLVED FIXED

People

(Reporter: mrbkap, Unassigned)

References

Details

This is a true edge case that came from bug 319123. The basic problem is the construct: // Document 1 document.write("<script src='document2.js'></script>Foo!"); // document2.js document.close() Before my fix for bug 319123, we used to not really respect the close() call and actually leak the parser and all of the related stuff. Now, we terminate the parser, but that means that we lose the "Foo!". IE seems to only respect the document.close after the document.write is done (i.e., a second document.write() after the one that closes the document actually starts a new document). I'm not sure what IE does with other <script>s after the document.close, though.
The fix in bug 321781 will cover this, I think.
Depends on: 321781
This should now behave the same as IE. Please reopen if not.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Summary: document.close handled from an external, is mildly incorrect → document.close handled from an external script, is mildly incorrect
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.