On Jun 2, 10:37 am, Boris Zbarsky <[EMAIL PROTECTED]> wrote: > Jonathan wrote: > > My understanding is for each DOM element, mozilla will create a Frame > > for paint/display. > > 0 or more frames, more precisely. > > > My question is does the Frame hierarchy mirrors the DOM hierarchy in > > the source html? > > Somewhat, but not precisely. > > > For example, will the TextFrame be the child of the ContainerFrame > > (for the DIV tag) and same as the table. > > For your <div> the TextFrame will be a child of the <div>'s BlockFrame, yes. > > > TextFrame->ContainerFrame(table cell)->ContainerFrame(table row)- > >> ContainerFrame(table). > > here the TextFrame will be a child of a BlockFrame which is a child of a > TableCellFrame which is a child of the TableRowFrame, which is a child > of the TableRowGroupFrame, which is a child of the TableFrame, which is > a child of the TableOuterFrame. This follows the DOM closely, but has a > block inside the table cell and has the inner/outer table thing to > handle captions. > > -Boris
Thank you Boris, for your detailed explanation. My understanding is when Mozilla paints a page, it walks thru the Frame hierarchy to paint each frame. Can you please tell me if mozilla walks thru the frame hierarchy in a depth first approach or breath first approach? _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
