it looks like noobs like me get no help with firebug related stuff here... On Mon, Feb 2, 2009 at 6:47 PM, John J Barton <[email protected]>wrote:
> > That kind of code would be in css.js or lib.js: > > http://code.google.com/p/fbug/source/browse/branches/firebug1.4/content/firebug/css.js > > jjb > > On Feb 2, 10:22 am, mark_is_new <[email protected]> wrote: > > Disclaimer: I have not gone through the source code myself. I'm > > relatively new to JavaScript and curious about some of Firebug's > > capabilities. > > > > What technique is Firebug using to calculate the cascaded, > > programmatically-derivded CSS values for a particular element? We are > > writing a function to traverse upward in the DOM tree until we find > > the particular CSS attribute we're looking for (and we have defaults > > set on the html element). > > > > It seems that Firebug is doing something much more efficient than this > > to achieve its performance; we can see the wait time for some of the > > calculations on our page depending on how many levels we're moving > > up. We recursively call the node.parentNode until we find the > > attribute we're looking for, and return it to the calling function. > > > > Is there a direct method of getting these values? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
