On 4月30日, 上午1时13分, Boris Zbarsky <[EMAIL PROTECTED]> wrote: > byang wrote: > > So, do Gecko use different rendering tree for different media? > > Yes. > > > If so, we can just use the same document without any clone. > > We do that right now, but the problem is that printing is not a synchronous > operation and problems can arise if the DOM mutates during printing.
Yes, and I think fork a DOM tree is a good solution when there is a mutation occurred when printing or some else. > > pseudo-class such as visited, link, hover and etc. can be dealt on > > the DOM tree, I think. > > Sure. Those aren't really relevant here. > > > But, pseudo-element indeed cause some problems > > because they are not presented in the DOM tree directly like other > > real elements. But, I think the nsStyleContext can be placed on the > > FrameTree for these pseudo-elements. > > And right now it's placed on the frametree in all cases... which is > conceptually simpler than having it on the DOM tree for some cases and on the > frametree in others. In particular, most frame operations don't have to worry > about whether the frame represents a pseudo-element or not. Thank you for your help, Boris. Thanks! Regards! Bo
_______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
