On Oct 9, 4:00 pm, Andrew R <[email protected]> wrote:
> Got to stop for today, but I see that chrome.js has its own global $
> function that is the same code as lib.js's $ function.
>
> Comparing all of the documents, I get this:
> FTS0: chrome.$ global function document: chrome://firebug/content/firebug.xul
> for ID: fbAdfvTypeMenu
> FTS0: reattach document: chrome://browser/content/browser.xul
> FTS0: lib.$ document: chrome://firebug/content/panel.html for ID:
> fbAdfvTypeMenu
panel.html is the content of the panel (an HTML document inside of a
browser element). So you won't find your id in there, it is either in
browser.xul or firebug.xul. So either you are executing this statement
in the wrong window or passing in a |doc| object that is for the panel
not the toolbar.
jjb
>
> So for some reason it is not finding my XUL element is the
> chrome://firebug/content/firebug.xul file, but it is finding it in
> chrome://browser/content/browser.xul. Using the "DOM Inspector"
> plugin, I do see my toolbar in the firebug window though, and this is
> working:
>
> Firebug.chrome.$('fbPanelSplitter')
>
> But not
> Firebug.chrome.$('fbAdfvTypeMenu')
>
> So it seems that something is amiss with my XUL when it is in the new
> window. I recently added a bindings.xml file to use XBL for some of my
> elements, I wonder if that could have caused any problems.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
