Open
Bug 99219
Opened 24 years ago
Updated 3 years ago
Investigate the possibility of not always computing the containing block's height in HTMLREflowState initialization
Categories
(Core :: Layout, defect, P2)
Core
Layout
Tracking
()
NEW
Future
People
(Reporter: attinasi, Unassigned)
References
Details
(Keywords: perf)
While working on bug 85016, the cost of computing the containing block's
computed height became high and we had to hack around it a bit and special-case
elements that are percentage-height in auto-height containers. There may be a
further optimization whereby we can eliminate the computation of the containging
block's size when the children do not need it. Something to look into anyway...
|
Reporter | |
Comment 2•23 years ago
|
||
Moving Mozilla 1.01 bugs to 'future' milestone with priority P1
I will be pulling bugs from 'future' milestones when scheduling later work.
Priority: -- → P1
Target Milestone: mozilla1.0.1 → Future
|
||
Comment 3•22 years ago
|
||
In fact, would it make sense to make all sorts of computations in
nsHTMLReflowState lazy? As long as we're careful not to introduce cyclical
dependencies...
Assignee: attinasi → misc
Status: ASSIGNED → NEW
Component: Layout → Layout: Misc Code
Priority: P1 → P2
QA Contact: cpetersen0953 → nobody
Target Milestone: Future → ---
|
||
Updated•22 years ago
|
Target Milestone: --- → Future
|
||
Updated•16 years ago
|
Assignee: layout.misc-code → nobody
QA Contact: nobody → layout.misc-code
|
||
Updated•7 years ago
|
Product: Core → Core Graveyard
|
Assignee | |
Updated•7 years ago
|
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
|
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•