On Wed, Aug 19, 2009 at 17:16, johnjbarton<[email protected]> wrote:
> On Aug 19, 8:04 am, Olivier Cornu <[email protected]> wrote:
>> On Wed, Aug 19, 2009 at 16:58, johnjbarton<[email protected]> 
>> wrote:
>> > On Aug 19, 6:12 am, Olivier Cornu <[email protected]> wrote:
>> >> I still have a few issues, though, that i'd like to fix before working
>> >> on the _complex_ case. For example, the "this" object in the right
>> >> side of the debugger seems to be wrong/empty (see attached
>> >> screenshot); is that a problem of context? Or scope?
>>
>> > In the image I see Firebug stopped on a break point in window.sub()
>> > and the 'this' value is the window. So it looks correct to me.
>>
>> But it's empty (notice "this" has been developed).
>> There usually is more stuff in there, for example when i debug a JS
>> script embedded in this same page.
>> Also, i suppose "this" should be the Sandbox in order to see things as
>> the debugged script does.
>
> I guess these two go together: the display is incorrect because the
> underlying data is not correct.

Probably.
I have troubles finding where in the code is "this" set. Would you be
so kind as to give me a clue?

> I don't know whether or not the sandbox should be "this", since the
> whole sandbox model makes not sense to me. I never could figure out
> what it did which is why we took it out of Firebug.

I'm no sandbox expert, but i understand it allows evaling code with
limited privileges.
A GM script sandbox uses the underlying window, wrapped into a XPCNW,
as its prototype. It seems there's more value in showing this rather
than the target window.


-- 
Olivier

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to