On Saturday 2009-09-19 18:27 +1200, Robert O'Callahan wrote: >> This is a really really good question. ;) I don't know. They have very >> different pathological behaviors. I would not be averse to trying the >> webkit approach, in general, and seeing what things look like. > > Right now it seems to me the only disadvantage of traversing the DOM > tree is that you have to examine every child of an element that has only > a small number of children that need restyling. But generally speaking > when we reflow or repaint we will examine all those children's frames > anyway, so avoiding looking at those child nodes doesn't seem like a > major win.
We could avoid this relatively easily by using an out-of-band tree (much like the reflow tree that we had before the reflow branch landed). This is what I propose in https://bugzilla.mozilla.org/show_bug.cgi?id=479655 (Another advantage such an approach might have is that we'd have more room for storing the various types of restyling we might want to do, if we want to differentiate more cases in order to optimize them.) -David -- L. David Baron http://dbaron.org/ Mozilla Corporation http://www.mozilla.com/ _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
