Closed
Bug 222730
Opened 22 years ago
Closed 22 years ago
[FIX]Possible optimization in reflow state (call CalcQuirkContainingBlockHeight less)
Categories
(Core :: Layout, defect, P1)
Tracking
()
RESOLVED
FIXED
mozilla1.6alpha
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
Attachments
(2 files)
1.65 KB,
patch
|
dbaron
:
review+
dbaron
:
superreview+
|
Details | Diff | Splinter Review |
5.34 KB,
patch
|
dbaron
:
review+
dbaron
:
superreview+
|
Details | Diff | Splinter Review |
It looks like we will often call CalcQuirkContainingBlockHeight even when the
frame in question doesn't have a percent height. Since
CalcQuirkContainingBlockHeight is not the fastest thing in the world, and since
we only need it if the frame has a percent height, I think we should add such a
check at this callsite.
Once this lands, I would be temped to change the "aRestrictToFirstLevel" switch
at this callsite to "false" and see what effect that has on Tp, as well as on
the regression tests.
Patch coming up; I've run the regression tests on it and they are happy.
![]() |
Assignee | |
Updated•22 years ago
|
Priority: -- → P1
Summary: Possible optimization in reflow state (call CalcQuirkContainingBlockHeight less) → [FIX]Possible optimization in reflow state (call CalcQuirkContainingBlockHeight less)
Target Milestone: --- → mozilla1.6alpha
![]() |
Assignee | |
Comment 1•22 years ago
|
||
![]() |
Assignee | |
Comment 2•22 years ago
|
||
Comment on attachment 133548 [details] [diff] [review]
Patch
David, could you review?
Attachment #133548 -
Flags: superreview?(dbaron)
Attachment #133548 -
Flags: review?(dbaron)
Comment on attachment 133548 [details] [diff] [review]
Patch
If this did regress anything, we'd want to know what was depending on this that
shouldn't be. r+sr=dbaron, but fix the comment 3 lines about what you changed.
Attachment #133548 -
Flags: superreview?(dbaron)
Attachment #133548 -
Flags: superreview+
Attachment #133548 -
Flags: review?(dbaron)
Attachment #133548 -
Flags: review+
![]() |
Assignee | |
Comment 4•22 years ago
|
||
Comment on attachment 133548 [details] [diff] [review]
Patch
Checked in, but doesn't seem to have much of an effect on Tp (if any). On the
other hand, I've just tested passing PR_FALSE for the aRestrictToFirstLevel
flag (with this patch already in, of course) and Tp was not affected. So I
think we should remove the whole aRestrictToFirstLevel optimization; I'll be
attaching a patch to that effect once I've run some regression tests... ;)
![]() |
Assignee | |
Comment 5•22 years ago
|
||
![]() |
Assignee | |
Comment 6•22 years ago
|
||
Comment on attachment 133594 [details] [diff] [review]
Proposed patch to remove the aRestrictToFirstLevel arg
David, what do you think? I ran this through the regression tests and there
are only four on which it made a difference:
5196, 50695-1, 88035-2, and 85016. In all these cases, the change makes us
render the testcase like IE does.
In fact, I would say this patch fixes bug 88035.
Attachment #133594 -
Flags: superreview?(dbaron)
Attachment #133594 -
Flags: review?(dbaron)
Attachment #133594 -
Flags: superreview?(dbaron)
Attachment #133594 -
Flags: superreview+
Attachment #133594 -
Flags: review?(dbaron)
Attachment #133594 -
Flags: review+
![]() |
Assignee | |
Comment 7•22 years ago
|
||
Fix checked in.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Core → Core Graveyard
Updated•7 years ago
|
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.
Description
•