Bommels05/Mozilla
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bug 240276. Make nsHTMLScrollFrame be a regular HTML frame, not a box frame, so we don't have to go through box layout. It gets its own reflow implementation that handles min-max and lots of other good stuff. rs+sr=dbaron,a=asa

Browse Source 
git-svn-id: svn://10.0.0.236/trunk@172836 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
roc+%cs.cmu.edu
2005-04-28 21:57:22 +00:00
parent ca0cb7e6fa
commit 131435cb9a
19 changed files with 842 additions and 754 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
mozilla/layout/generic/nsObjectFrame.cpp
View File

@@ -1434,7 +1434,11 @@ nsObjectFrame::HandleChild(nsPresContext* aPresContext,
// style context, so we simply want to reflow the child with pretty
// much our own reflow state, in the case of a broken plugin, the
// child has its own style context, so we create a new reflow
// state.... XXXbz maybe we should always have a different style context?
// state....
// XXXbz maybe we should always have a different style context?
// XXXroc no, that seems to break things. But as is, this causes
// an assertion failure in nsContainerFrame because the reflow
// state isn't built for the right frame.
nsReflowStatus status;