Closed Bug 323926 Opened 19 years ago Closed 17 years ago

nsCSSFrameConstructor::GetInsertionPoint should use nsIFrame::GetContentInsertionFrame

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: dbaron, Unassigned)

References

Details

nsCSSFrameConstructor::GetInsertionPoint does fixup for scrollframes that seems just like what the nsIFrame::GetContentInsertionFrame for scrollframes does. I think it should use nsIFrame::GetContentInsertionFrame in general to fix similar bugs for all the other frames that implement nsIFrame::GetContentInsertionFrame. Does this make sense?
Yeah, I guess. At least it'll make us consistently buggy in the cases when we're buggy (that is, for example, any time we're dynamically adding kids to something that has a content insertion frame).
This got fixed by the patch in bug 348049.
Status: NEW → RESOLVED
Closed: 17 years ago
Depends on: 348049
Resolution: --- → FIXED
Product: Core → Core Graveyard
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.