Firebug decompiles the document object. So it starts with window.documentElement and walks all of the childNodes and their children recursively. Well actually it doesn't do that ;-). It starts with the currently selected element and walks it parents to the root and the children, rendering one branch from root to leaf. Then if you visit siblings it remembers the branches it has already rendered.
jjb On Jun 7, 7:50 am, barz1 <[email protected]> wrote: > Okay, I have been working with my companies front end which is now a > pretty large google web toolkit application. I have tried with other > tools such as HTMLUnit and HTTPunit to pull the html from the web > page, but all I get is the head section listing numerous javascript > references and functions. When I examine the site using firebug, the > body html of the application is displayed, I guess I am just wondering > if anybody knows how firebug approaches generating the html or DOM for > a site.Thanks! -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
