Closed Bug 209607 Opened 21 years ago Closed 19 years ago

Should not ever call GlobalWindowImpl::SetNewDocument(nsnull)

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: caillon, Unassigned)

References

Details

We need to clean up the code that calls SetNewDocument with a null
nsIDOMDocument argument.  In bug 163645, I am going to add a new
|nsCOMPtr<nsIXPConnectJSObjectHolder> mNavigatorHolder;| member because we need
to hold on to the navigator in between SetNewDocument calls, in between which we
may be GC'd.  If we fix this, it would remove the need for this as we could
simply re-root the navigator object in the same function without having to worry
about potential GC's in between calls.
QA Contact: desale → ian
This will be fixed by bug 296639.
Depends on: splitwindows
This is now fixed (by bug 296639).
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.