Thanks for the speedy reply, Do you think doing this for NetExport and ConsoleExport would be worth doing? Or would that be a security risk?
I think it could hugely help with recording details of acceptance testing runs. Particularly for AJAX driven pages that couldn't rely on the page reload to trigger exporting. On Tuesday, 9 October 2012 16:16:04 UTC+1, Jan Honza Odvarko wrote: > > From some reason this question didn't make it into the Web UI of the > newsgroup. > > > Can Firebug or a Firebug extension expose functionality to the web page > that > > is being viewed through javascript? > Yes, this is e.g. how the Console object or Command line API are > exposed to the page content. > > Of course, you need to make sure there is no a security issue since > you are opening chrome > space API to the world (== to the page content). > > Honza > > --- > From: [email protected] <javascript:> [mailto: > [email protected] <javascript:>] On > Behalf Of Kieran Shaw > Sent: Tuesday, October 09, 2012 4:52 PM > To: [email protected] <javascript:> > Subject: [firebug] Javascript interface to interact with Firebug and > plugins? > > Can Firebug or a Firebug extension expose functionality to the web > page that is being viewed through javascript? > > For example, could the NetExport extension be forced to trigger an > export by doing something like: Firebug.NetExport.export() > > Any ideas? > > 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 https://groups.google.com/forum/#!forum/firebug
