Closed
Bug 323105
Opened 19 years ago
Closed 5 years ago
consider removing DeletingFrameSubtree
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
DUPLICATE
of bug 508473
People
(Reporter: dbaron, Assigned: sicking)
References
Details
I think we should consider removing DeletingFrameSubtree, by doing the following: * change the rules so that out-of-flow frames are always destroyed through their placeholder, and things like nsAbsoluteContainingBlock and nsBlockFrame (for float list) just *assert* at the end of their Destroy that there are no out-of-flow frames left * make placeholder frame's destructor do UnregisterPlaceholderFrame * move the removal from primary frame map to the end of nsFrame::Destroy, and make it do something that checks to make sure it's removing the right frame * also do aFrame->RemovedAsPrimaryFrame(aPresContext); aFrameManager->ClearAllUndisplayedContentIn(content); somewhere in nsFrame::Destroy
Reporter | ||
Comment 1•19 years ago
|
||
See also the cleanup in bug 310638.
Assignee | ||
Comment 3•19 years ago
|
||
Making dependency go the other way around. It'll be easier to do this once mats patch is checked in.
Comment 4•5 years ago
|
||
DeletingFrameSubtree
has been deleted in bug 508473 Part II, and our frame destruction mechanism should have been improved since then.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•