Followup from bug 233463 comment 62 --
From Boris Zbarsky (:bz) 2009-08-25 08:44:30 PDT:
For that matter, I'm not quite sure why we have separate nsHTMLContainerFrame
and nsContainerFrame, but that's also fodder for a separate bug.
dbaron, roc, is there a point to having these be separate classes?
I don't think so.
Created attachment 584162 [details] [diff] [review]
There was one issue - both nsHTMLContainerFrame, nsContainerFrame
implements BuildDisplayList. Identically, except nsHTMLContainerFrame
uses DISPLAY_CHILD_INLINE and nsContainerFrame does not.
Investigating all classes that inherit nsHTMLContainerFrame...
implements BuildDisplayList that explicitly calls nsHTMLContainerFrame::BuildDisplayList
does not implement BuildDisplayList
I made the above four have a BuildDisplayList that calls a new (protected)
convenience method BuildDisplayListForInline that implements the
The remaining derived classes all implements BuildDisplayList but
does not call nsHTMLContainerFrame::BuildDisplayList.