Good point, hopefully FF will make their sandbox more developer friendly in upcoming releases.
The injecting a script tag into the page: how do you then time code in your extension so that it runs after the code has been injected? Do you use firefox events to notify the extension? -Andrew On Fri, Jan 30, 2009 at 9:31 AM, John J Barton <[email protected]> wrote: > > Antonin's code probably targets 1.4. > > I spent a lot of time with the FF sandbox thing. I eventually gave up > and created the monster we have now for command line evaluation. The > sandbox thing was more a "quicksand box". Every time you tweak it or > try another case it breaks in some way. > > If your goal is to create an object in the page the easy way is to > inject a script tag in the page. This is safe for users of your > extension and you know exactly how it works. > > jjb > > > On Jan 30, 8:11 am, Andrew R <[email protected]> wrote: >> Thanks, that helped, although I had to tweak the code to get it to >> work in Firebug 1.3.0 (Firebug.CommandLine.isReadyElsePreparing no >> longer exists). >> >> Hopefully the firebug API settles down a bit and things get easier for >> extenders. I'd still really love to know why the code doesn't work in >> the FF sandbox though. Everything seems to work, except the "new >> SomeObject". > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
