Reported as a bug:
http://code.google.com/p/fbug/issues/detail?id=2402
Thank you
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Firebug group.
To post to this group, send email to firebug@googlegroups.com
To
I think this may be a bug in Firefox at this point, but I am truly
confused.
I added this code to the reattach function of my panel:
logger.info('reattach: Menu using document of chrome: %s',
Firebug.chrome.window.document.getElementById('fbAdfvTypeMenu'));
var walker = doc.createTreeWalker
Found it!
Apparently XUL got a little unhappy with me with overlaying too many
elements. I removed some of the fb* elements that weren't necessary in
my overlay and it started working again.
Thanks for your help and sorry to waste your time.
--~--~-~--~~~---~--~~
Found it!
It looks like the XUL of firebug is different in the window than when
it is docked. Using the DOM inspector I found that instead of the
innerToolbar being in a XUL toolbar, it is actually in a panelBar when
opened in a new window. I had it mapped in my XUL being in a toolbar
and thus
Okay, there is more to it than that. Firebug's XUL, when opened in a
new window has 2 toolbox's with the ID fbToolbox
There is one as a direct child of the window object that contains the
menubar and there is another that is in the vbox in the box with id
fbPanelPane. I started adding my own
Thank you for that information, apparently something is askew with my
Firebug.chrome in my panel. I have this code:
const superClass = Firebug.ActivablePanel;
OAdfvPanel.prototype = extend(superClass,
{
...
reattach: function (doc)
{
logger.trace('OAdfvPanel.reattach: %s', doc);
try
On Oct 9, 8:59 am, Andrew R andrew.rw.robin...@gmail.com wrote:
Thank you for that information, apparently something is askew with my
Firebug.chrome in my panel. I have this code:
...
Firebug.chrome.$('fbAdfvTypeMenu')
Is returning null
So the |document| in the scope that chrome.js was
This is what I have:
My chrome.manifest:
content oracleadfv content/
resourceoracleadfvdocs docs/
locale oracleadfv en-US locale/en-US/
skinoracleadfv classic/1.0 skin/
overlay chrome://firebug/content/firebugOverlay.xul
On Oct 9, 1:26 pm, Andrew R andrew.rw.robin...@gmail.com wrote:
Roughly speaking I don't see anything obvious.
I would add
FBTrace.sysout(lib.$ document: +(doc?
doc.location:document.location) );
in lib.js this.$ function and see where it thinks you are when you get
null values for
Thanks, that has exposed the problem but not the source of the
problem.
I changed this in chrome.js:
$: function(id)
{
FBTrace.sysout(chrome.$ document: +(document.location) + for ID:
+ id + and $ is: + $);
return $(id);
},
And this in lib.js:
this.$ = function(id, doc)
{
Okay, this is really odd.
After adding the logging in both lib.$ and chrome.$ in the firebug
code, I found something really odd. When firebug is inside firefox,
everything is cool and the global $ as seen by chrome.$ is the same
as FBL.$, but when I open firebug in a window, I get a different $
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:
On Oct 9, 3:41 pm, Andrew R andrew.rw.robin...@gmail.com wrote:
Okay, this is really odd.
After adding the logging in both lib.$ and chrome.$ in the firebug
code, I found something really odd. When firebug is inside firefox,
everything is cool and the global $ as seen by chrome.$ is the
On Oct 9, 4:00 pm, Andrew R andrew.rw.robin...@gmail.com 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:
A user of my extension has realized that errors occur when firebug is
opened in a new window. The reason is that Firebug.chrome.$(id) was
returning null when I called a function during reattaching. Unlike the
firebug code, I haven't been keeping local variables around to point
to the DOM
On Oct 8, 5:06 pm, Andrew R andrew.rw.robin...@gmail.com wrote:
A user of my extension has realized that errors occur when firebug is
opened in a new window. The reason is that Firebug.chrome.$(id) was
returning null when I called a function during reattaching. Unlike the
firebug code, I
16 matches
Mail list logo
