Hi Andrew, I'm not firefox expert and I know almost nothing about eval-ing javascripts in sandboxes but I was in the same need of executing arbitrary javascript in the context of running page and possibly getting results back to my firebug extension.
I've ripped part of new firebug's commandline functionality and monkey- patch some other bits: http://github.com/darwin/firequery/blob/2fcd979cd28d5afda00bcdcf57e721c8323e015c/firefox/chrome/content/firequery.js#L110 regards, Antonin On Jan 30, 8:16 am, Andrew R <[email protected]> wrote: > By the way, I am not using Firebug.CommandLine.evaluate* methods, due > to the fact in version 1.3, they fail when I call them from my > extension. It seems like 1.3 needs to run some setup before I am > allowed to call those methods (they are not initialized correctly when > my panel is the current one and I am triggering off of my panel's show > event). > > Still I am baffled why the 'new ...' would not return me a new object, > but instead give me the component. > > Also note that if I run the code in the firebug console command line, > not from my extension's code, everything works. The problem is that I > am having problems determining how in 1.3 of FB to have my extension > act like a user running code in your command line. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
