On Nov 25, 5:11 pm, Manoj <[EMAIL PROTECTED]> wrote:
> Your suggestion works like a charm.
>
> Is it appropriate to use context.uid as the key to associate all the
> data (network/DOM/JS).
No, context.uid is just a sanity check for when I'm confused about
contexts. For example the contextUID appears in the panelNode in
chromebug.
> In that case, how do I map the initial request (root document) into
> the appropriate firebug context. This is because, the first time, I
> try to get the context in observe() using:
>
> var win = getWindowForRequest(subject);
> var context = TabWatcher.getContextByWindow(win);
>
> starting with about:blank, the first navigation results in context
> being null.
I'm not sure what you mean by starting with about:blank.
Do you see the initContent in the trace? If you issue
FBTrace.sysout(..);
in your code and see trace option DISPATCH and WINDOWS you should see
your event relative to the context creations.
Or win is not what you think...
FBTrace.sysout("your text", win);
to look at it.
>
> Subsequent navigations, return the previous context (the one about to
> be destroyed.) The framework calls initContext() after the initial
> request.
Sorry you lost me here.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
