On Jun 6, 10:57 pm, Boris Zbarsky <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > These dynamic changes are caused by manipulations of the content model > > via the DOM (generally through java script). When a content element is > > modified, added or removed, Layout is notified. > > Specifically via the nsIMutationObserver interface implemented by the > presshell. > > > If content elements have been inserted, new frames are created > > By nsCSSFrameConstructor, which gets notifications from the presshell. > > > and formatted(and impacts > > to other frames are managed by performing further incremental > > reflows). > > All this happens asynchronously; at the time of the DOM mutation an event is > posted to do a reflow sometime later. > > > Can tell me which class and which methods of the class in 'Layout' is > > notified when a new frame is created/formatted > > PresShell::FrameNeedsReflow, if you're really asking what you typed.... > > > which is used for incremental reflows? > > There is no longer much of a distinction between incremental and > non-incremental > reflows in terms of codepath; what really matters is which frames are marked > dirty. > > -Boris
Boris, Thank you for the very detailed explanation. I assume JavaScript execution will be executed 'incrementally'? As Gecko see a Script node in the Document, it will call the javascript engine for the js exection. Is there a corresponding interface for that (just like nsIMutationObserver fpr CSS)? Thank you. _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
