Access to the window object via the wrappedJSObject should be
minimized since each case needs to be analyzed for security
implications. You don't want to call a method on an object pointing
directly into a web page.
jjb
On Dec 8, 10:17 pm, LiuCougar <[EMAIL PROTECTED]> wrote:
> Hi peller :)
>
> I think you are talking about extension for FF3
>
> change it to this:
> watchWindow: function(context, win){
> win.wrappedJSObject.testing="123";
> }
>
> and it should work just fine
>
> liucougar
>
>
>
> On Mon, Dec 8, 2008 at 22:01, Adam Peller <[EMAIL PROTECTED]> wrote:
>
> > I am a n00b at extensions writing. I took the simple Test Panel demo
> > and tried adding the following code to the FirebugTestExtension
> > module:
>
> > watchWindow: function(context, win){
> > win.testing="123";
> > }
>
> > I've confirmed in my extension code (with alerts -- dump didn't seem
> > to send anything to my MacOS terminal window) that the method is
> > getting called and win.testing is being set, each time a window is
> > created. However, from the page, window.testing is undefined.
>
> > What am I missing? Is this a different window reference than the one
> > that is my global?
>
> --
> 生于忧患，死于安乐
> "People's characters are strengthened through struggle against
> difficulties; they are weakened by comfort."
> - Old Chinese adage
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
