Open
Bug 76767
Opened 24 years ago
Updated 2 years ago
refactor nsBlockFrame
Categories
(Core :: Layout: Block and Inline, defect, P5)
Tracking
()
NEW
Future
People
(Reporter: dbaron, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug)
Details
I think at some point nsBlockFrame needs a major cleanup. Here are some ideas I think might work (although I haven't thought them through well enough yet to really have a good idea how they might work): * It would be good to store vertical margins in separate structures, say, nsBlockVerticalMargin (or maybe something a little shorter), since a single vertical margin can be associated with an arbitrary number of blocks. * It might (I've thought about this even less) be nice to split nsBlockFrame into two classes: nsBlockFrame and nsBlockInnerFrame -- the outer one would contain only other block frames, tables and nsBlockInnerFrames, and the inner one would serve as a container for lines. The current way the mLines array stores both block and inline children has always seemed weird to me and I think the code might end up being simpler if we distinguished between them. Or something like that... I'm not sure if other people had been thinking about similar things, but I wanted to jot these ideas down in a bug before I forgot them...
Reporter | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Updated•23 years ago
|
Target Milestone: --- → Future
Reporter | ||
Updated•23 years ago
|
Priority: -- → P5
Reporter | ||
Updated•22 years ago
|
Component: Layout → Layout: Block & Inline
Updated•15 years ago
|
QA Contact: chrispetersen → layout.block-and-inline
Reporter | ||
Updated•4 years ago
|
Assignee: dbaron → nobody
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•