Closed Bug 251501 Opened 21 years ago Closed 21 years ago

refactor handling of where frames get inserted for child content

Categories

(Core :: Layout, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: roc, Assigned: roc)

Details

Attachments

(1 file, 1 obsolete file)

Currently nsCSSFrameConstructor::GetFrameFor has some ghastly code to figure out where to insert the frames for child content. It would be much better to replace this with a method on nsIFrame that determines where child content frames should be inserted.
Attached patch fix (obsolete) — Splinter Review
The reason I need this, by the way, is because columns need similar delegation and I couldn't bear to extend GetFrameFor. But this code cleanup feels good on its own.
This is the right patch
Attachment #153254 - Attachment is obsolete: true
Attachment #153255 - Flags: superreview?(dbaron)
Attachment #153255 - Flags: review?(dbaron)
Comment on attachment 153255 [details] [diff] [review] that was the wrong patch... What's up with ConstructBlock? You're changing the callers and the signature without changing the function itself. I'm assuming that's for some other patch and you just forgot to remove it. Other than that this seems fine.
Attachment #153255 - Flags: superreview?(dbaron)
Attachment #153255 - Flags: superreview+
Attachment #153255 - Flags: review?(dbaron)
Attachment #153255 - Flags: review+
Correct. The ConstructBlock changes are for the actual column frame implementation and I forgot to edit them out. Thanks.
checked in
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: