Closed
Bug 227421
Opened 21 years ago
Closed 8 years ago
Document transition unsets the document pointer in the old DOM tree
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 209607
People
(Reporter: jst, Assigned: jst)
Details
(Whiteboard: [expired?])
When we leave a page, we go through the whole DOM tree calling
SetDocument(nsnull) on every node to signal that the document is no longer
displayed. This causes lots of problems and complicates things, and it also
plays in to the whole problem of the document being cleared in a window when
it's closed, etc. This should be cleaned up at some point, but doing so will be
a rather tricky and large change...
Comment 1•21 years ago
|
||
Is the better way to create some proxies for window objects, such that the old
doc can live in its proxy, and the new one can load into a new proxy, and never
the twain shall meet?
/be
Assignee | ||
Comment 2•21 years ago
|
||
Brendan, from all I've seen when testing how IE deals with this yes, that's the
way to go. But even with that, we need to not stomp throug the document and
reset mDocument etc, there's more to fix here than what meets the eye, I'm sure.
Comment 3•21 years ago
|
||
I think I already filed this as bug 209607.
Updated•15 years ago
|
QA Contact: ian → general
Updated•15 years ago
|
Whiteboard: [expired?]
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•