canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,334
edits
Gecko:Reflow Refactoring: Difference between revisions
→Future Development Tasks
(→Quick Links: tinderbox) |
|||
| Line 197: | Line 197: | ||
* should table special height reflows mark dirty or ensure nsHTMLReflowState::mFlags.mVResize is set and depend on vertical resize optimizations? | * should table special height reflows mark dirty or ensure nsHTMLReflowState::mFlags.mVResize is set and depend on vertical resize optimizations? | ||
* We can end up in a state where <code>mDirtyRoots</code> is empty after a <code>FrameNeedsReflow()</code> call -- when <code>nsGfxScrollFrameInner::LayoutScrollbars</code> sets attributes on the slider we end up in <code>nsSliderFrame::AttributeChanged</code> which calls FrameNeedsReflow(). Should we be checking that boolean that the scrollframe uses to tell itself that it's not a real curpos change? | * We can end up in a state where <code>mDirtyRoots</code> is empty after a <code>FrameNeedsReflow()</code> call -- when <code>nsGfxScrollFrameInner::LayoutScrollbars</code> sets attributes on the slider we end up in <code>nsSliderFrame::AttributeChanged</code> which calls FrameNeedsReflow(). Should we be checking that boolean that the scrollframe uses to tell itself that it's not a real curpos change? | ||
* debug assertions related to special height reflows in gmail *compose* | |||
== Future Testing Tasks == | == Future Testing Tasks == | ||