Closed Bug 24292 Opened 25 years ago Closed 25 years ago

Lots of style changed reflow commands

Categories

(Core :: Layout: Form Controls, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: troy, Assigned: rods)

References

()

Details

(Whiteboard: Fix is in my tree)

Rod, if you load up http://www.cnn.com/ you'll notice lots of StyleChanged incremental reflow commands targeted at a nsListControlFrame frame There are also lots of StyleChanged reflow commands targeted at a nsGfxButtonControlFrame frame as well All of these incremental reflows slow down the document load, of course
Troy, I need a some help here. Is the ListControlFrame responsible for all the StyleChange reflows? Or is it that it doesn't handle them efficiently? What do you think is the problem in the ListControlFrame that I should look at fixing? Thanks.
Target Milestone: M14
setting milestone to M14
I don't know why the StyleChanged() reflow commands are happening. Probably because the style system thinks the style context needs to be re-resolved (although I don't know the answer to why of that question either). You're probably handling them efficiently, unfortunately, StyleChanged is a very inefficient process because it requires reflowing that entire frame subtree (recursively, no shortcuts). I'll take a look and see if I can tell why the style system is generating the StyleChanged reflow commands. I was kind of hoping you knew. :-)
Troy, The Combobox is changing incremental reflows to StyleChanged reflows, this has been there a very long, long time. I am not even sure why.
Status: NEW → ASSIGNED
Whiteboard: Fix is in my tree
Fix is in my tree
Is the fix going into M14? And how would one go about testing this bug? From the comments it sounds like more of an under-the-covers type of bug that doesn't manifest itself in an obvious fashion. I could, however, be complete wrong. Any comments/suggestions?
changing to M15
Target Milestone: M14 → M15
This has been fixed with my lastest checkin
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Updating QA contact.
QA Contact: ckritzer → bsharma
Verified build 2001080608 os:winNT
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.