Re: installation error
Never mind. FF 3.5.3 appears to just have a hard time . see ... http://support.mozilla.com/eu/forum/1/461104 On Oct 8, 9:39 pm, Cassiopeia n...@baytides.ca wrote: - running FF3.5.3 and FB 1.4.3 on Vista Business. - since the last FB upgrade, FB is no longer available. The extension.log in my FF profile shows [code] 2009-10-08 21:33:14 - safeInstallOperation: install operation (caller- supplied callback) failed, rolling back file moves and aborting installation. 2009-10-08 21:33:14 - safeInstallOperation: failed to remove the folder we failed to install an item into: C:\Users\\AppData \Roaming\Mozilla\Firefox\Profiles\bbmkvysh.default\extensions \fire...@software.joehewitt.com -- There is not much to suggest here... maybe restart and try again? 2009-10-08 21:33:14 - ExtensionManager:_finishOperations - failure, catching exception - lineno: 565 - file: undefined - [Exception... Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.remove] nsresult: 0x80004005 (NS_ERROR_FAILURE) location: JS frame :: file:///C:/Program%20Files/Mozilla%20Firefox/components/nsExtensionManager.js :: removeDirRecursive :: line 565 data: no] 2009-10-08 21:33:14 - safeInstallOperation: install operation (caller- supplied callback) failed, rolling back file moves and aborting installation. 2009-10-08 21:33:15 - ExtensionManager:_finishOperations - failure, catching exception - lineno: 1658 - file: undefined - [Exception... Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIZipReader.extract] nsresult: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) location: JS frame :: file:///C:/Program%20Files/Mozilla%20Firefox/components/nsExtensionManager.js :: extractExtensionFiles :: line 1658 data: no] 2009-10-08 21:33:15 - ExtensionManager:_finishOperations - failure, catching exception - lineno: 4987 - file: file:///C:/Program%20Files/Mozilla%20Firefox/components/nsExtensionManager.js - TypeError: entries[i] is null [/code] Hopefully there is a fix or if I'm missing something??? Since FB worked fine before the last upgrade I'll try and go back to an earlier version. --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~--~~~~--~~--~--~---
Re: Firebug Add-on installed, no idea where to open
I've no experience of FEBE, but I notice it's had lots of five star reviews, and then just recently two with complaints about corrupted files. It's another Extension, so could it be having trouble with FF 3.5.3 like the rest of us ? WD is more important to me than FB, so I'm going to leave the latter off until there's a fix. Tim On Oct 9, 4:06 am, gollum gollum.g...@gmail.com wrote: The FEBE[1] extension has an option to check/correct the extension directory. Don't know how well it works, haven't had that problem ... so far ;-} [1]https://addons.mozilla.org/en-US/firefox/addon/2109 On Oct 9, 12:18 pm, Cassiopeia n...@baytides.ca wrote: just fyi, I'm experiencing the same issues. FF3.5.3 upgrade and FB gone. WD still there and works as usual. I remember an automatic FB upgrade yesterday?, FB has not been seen since. Nora On Oct 8, 5:20 pm, ramasaig t...@ramasaig.com wrote: Noah, Iff your FB problem is similar to mine with Web Developer, the order of operations needs to be different: Open FF Install Firebug in the usual way Restart FF (you may be able to omit this step, but you can check for FB in the 'Tools Add-ons' list) Close FF (make sure it really is closed in 'Task Manager Processes') Go to Profile, delete 'extensions.*' files Restart FF I'm running XP, your Vista terminology may be different. I'm having trouble with Firebug not installing properly too, and unfortunately the above procedure doesn't seem to solve it. When I've installed FB, I can see it listed in the 'Tools' menu, with an arrow on the right that doesn't produce a further menu. Is it the same for you ? My troubles started with FF 3.5.2 and the new Google Toolbar (supposedly compatible). In addition to the vanishing WD, legitimate pop-ups (e.g. enlarged images) won't work when certain extensions are present (X-marks particularly). Pop-ups don't work when I've installed FB either, but this may be due to the faulty install rather than FB itself. Also, when the install is faulty FF doesn't always close properly, and I have to do it in 'Task Manager Processes'. I fear that won't help you much, but at least you'll know you're not alone. Tim On Oct 8, 9:16 pm, noahpke n...@peacekeeper.com wrote: Alexa Sparky 1.4.4 installed successfully. --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~--~~~~--~~--~--~---
Re: A little geek entertainment...
You are trying to use E4X syntax on something that isn't an XML object - http://en.wikipedia.org/wiki/ECMAScript_for_XML Correct use of that syntax: var data = rootvalue a=1foo/valuevalue a=1bar/ valuevalue a=2bas/value/root; alert(data.value.(@a == 1)); bar is also a valid filter but it is a useless one - it is the equivalent of true. --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~--~~~~--~~--~--~---
Re: A little geek entertainment...
On Oct 9, 2:20 am, Wladimir Palant trev@adblockplus.org wrote: You are trying to use E4X syntax on something that isn't an XML object -http://en.wikipedia.org/wiki/ECMAScript_for_XML Correct use of that syntax: var data = rootvalue a=1foo/valuevalue a=1bar/ valuevalue a=2bas/value/root; alert(data.value.(@a == 1)); bar is also a valid filter but it is a useless one - it is the equivalent of true. Yes, more evidence that E4X is a bug. Embedding non-core features in to Javascript by cute syntax degrades the language. Here is the back story. I got the error message, which included by the way, a complete copy of the web page (yes, in the error message text!). I had no idea why or where this came from, in part because the line number for the error message was at the end of the error message, many hundreds of characters off screen. When I did find the line number I saw what had happened. Some time ago I had been searching through the source for getScriptAnalyzer. I must have ended the search on a line like var f = sourceBox.getScriptAnalyzer(script); with the method name selected. I that point I got distracted and sometime later hit the keyboard, deleting the method name: var f = sourceBox.(script); Before cutesy E4X syntax corruption, this line would have been a simple syntax error. Now this line becomes a bizarre error message (but could also have been a valid line that did something). For reasons like this E4X is not an architectural building block, layering on the foundation of the JS language to enhance it for a subcategory of users. Instead it is a corruption, infiltration of the language forcing everyone to deal with the XML mistake. Or I need to be more careful typing, ;-) jjb jjb --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~--~~~~--~~--~--~---
Re: Extending firebug: Understanding Firebug.chrome.$(id) vs. FirebugChrome.$(id) vs $(id)
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
{
superClass.reattach.apply(this, arguments);
logger.info('Menu using firebug.chrome: %s', Firebug.chrome.$
('fbAdfvTypeMenu'));
logger.info('Menu using document: %s', document.getElementById
('fbAdfvTypeMenu'));
...
Firebug.chrome.$('fbAdfvTypeMenu')
Is returning null
document.getElementById('fbAdfvTypeMenu')
Is returning my element in the XUL toolbar
The relevant portion of my XUL is this:
...
toolbox
id=fbToolbox
toolbar
id=fbToolbar
hbox
id=fbToolbarInner
class=innerToolbar
insertbefore=fbDetachButton
align=center
hbox
id=fbAdfvFbButtons
insertafter=fbNetButtons
collapsed=true
toolbaritem align=center
label
class=oadfv-toolbar-label
value=oadfv.typelabel;
tooltiptext=oadfv.typemenu.tt; /
/toolbaritem
toolbarbutton
id=fbAdfvTypeMenu
type=menu
role=button
tooltiptext=oadfv.typemenu.tt;
aria-haspopup=true
oncommand=return Firebug.OAdfvModule.onTypeMenuCommand
(event, FirebugContext)
...
any idea why the Firebug.chrome is not finding the toolbarbutton by
ID, but a plain old document.getElementById is working? Makes me
wonder if I should just use document.getElementById instead of $ in my
extension. Is it possible that I am doing something that would cause
the Firebug.chrome.$ to see the wrong document but the global document
in my panel to be the correct one (I have a lot of code in my
extension, so it is very plausible that I have a bug causing this
behavior)?
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to
firebug+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~--~~~~--~~--~--~---
Re: Extending firebug: Understanding Firebug.chrome.$(id) vs. FirebugChrome.$(id) vs $(id)
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 compiled in has no
element with that id.
document.getElementById('fbAdfvTypeMenu')
Is returning my element in the XUL toolbar
Then the |document| in the scope of this statement does have the
element.
I guess the code is included via a script tag in your overlay's .xul
file. I guess you are overlaying browser.xul but I think you need to
overlay firebug.xul?
jjb
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to
firebug+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~--~~~~--~~--~--~---
Re: Something happen to break on error in svn?
How does this work when you want to debug something that happens when the page loads? If I hit the pause and reload the page, the throbbing pause is gone. So how to debug breaking things at the start of the page before I get a chance to race over to the pause button? On Oct 5, 5:02 pm, johnjbarton johnjbar...@johnjbarton.com wrote: On Oct 5, 4:53 pm, Steven Roussey srous...@gmail.com wrote: Hitting the pause button breaks into timer code though... So it keeps breaking all the time, which isn't so useful (unless you are debugging times or events, etc). The pause button in the console panel? jjb On Oct 2, 8:33 pm, johnjbarton johnjbar...@johnjbarton.com wrote: On Oct 2, 4:00 pm, Steven Roussey srous...@gmail.com wrote: Something happen to break on error in svn? The option seems to have disappeared.. The short answer: use the pause button || on the Console now. The long version: It just moved to the Console panel. This is part of our overall Break On Anything! for 1.5. Console || == Break on Next Error Errors in the console: break on specific lines with errors. HTML || == Break on Next Mutate Element in the console: break on mutation to specific elements Script || == Break on Next JS statement Source line: break on next execution of this line DOM || == Break on next property update (maybe) DOM panel row: break on property change CSS || == Break on any style change CSS selector: break on selector changed CSS rule: break on rule changed. In addition: all the different kinds of break points will be listed in the Breakpoints side panel; as far as possible they will all support conditional expressions; the new breakpoint notification will report the reason/condition of the break. jjb --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~--~~~~--~~--~--~---
Re: Extending firebug: Understanding Firebug.chrome.$(id) vs. FirebugChrome.$(id) vs $(id)
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
chrome://oracleadfv/content/FirebugOverlay.xul
style chrome://firebug/content/firebugOverlay.xul
chrome://oracleadfv/skin/overlay.css
The start of my chrome://oracleadfv/content/FirebugOverlay.xul:
?xml version=1.0?
!DOCTYPE oadflocal SYSTEM chrome://oracleadfv/locale/mainPanel.dtd
overlay
xmlns=http://www.mozilla.org/keymaster/gatekeeper/
there.is.only.xul
...
script type=application/x-javascript
src=mainModule.js/
script type=application/x-javascript
src=mainPanel.js/
...
toolbox
id=fbToolbox
...
I went off of the Firebug blog posts when I changed my extension to
start extending firebug:
http://www.softwareishard.com/blog/firebug-tutorial/extending-firebug-hello-world-part-i/
So I should not have anything that is overlaying firefox at this
point, only firebug.
Here is some of the start of my panel:
FBL.ns(function () { with (FBL) {
if (!Firebug.OAdfvModule) { return; }
const utils = Firebug.OAdfvUtil;
const logger = Firebug.OAdfvLogger;
//
const superClass = Firebug.ActivablePanel;
const adfvext = Firebug.OAdfvModule;
const panelName = 'adfvMainPanel';
// Local STR function that adds the panel name and uses our bundle
function $LSTR(name)
{
return $STR(panelName + '.' + name, utils.bundleName);
}
function $LSTRF(name, args)
{
return $STRF(panelName + '.' + name, args, utils.bundleName);
}
try{
function OAdfvPanel()
{
logger.debug('OAdfvPanel created');
}
...
Firebug.registerPanel(OAdfvPanel);
Firebug.OAdfvPanel = OAdfvPanel;
} catch (e) {
//Firebug.Console.log(e);
logger.error(e);
}
}});
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to
firebug+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~--~~~~--~~--~--~---
Firebug debugging is not working
I'm using Firefox 3.0.12 on Windows and Firebug 1.4.3 When I set and exercise a break point nothing happens. I was so sure it is user error that I watched the Firebug video and used this exact example in the video: Went to getfirebug.com. Set a breakpoint in the onClickTab method on this line: if (img.className == topTab) Next, I clicked on a tab. The tab worked like in the video. I allowed Javascript in my NoScript 1.9 add-on, however, firebug did not do anything. There is nothing in the Error Console. Does anyone have any ideas? Thanks, jc --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~--~~~~--~~--~--~---
Re: Something happen to break on error in svn?
On Oct 9, 12:31 pm, Steven Roussey srous...@gmail.com wrote: How does this work when you want to debug something that happens when the page loads? If I hit the pause and reload the page, the throbbing pause is gone. So how to debug breaking things at the start of the page before I get a chance to race over to the pause button? Well let's make up a story and see if we can get it to work. If you hit pause on the net panel and reload what stop point will make sense? If you hit pause on the script panel and reload I think it should break on the first JS statement in the page. Others? On Oct 5, 5:02 pm, johnjbarton johnjbar...@johnjbarton.com wrote: On Oct 5, 4:53 pm, Steven Roussey srous...@gmail.com wrote: Hitting the pause button breaks into timer code though... So it keeps breaking all the time, which isn't so useful (unless you are debugging times or events, etc). The pause button in the console panel? jjb On Oct 2, 8:33 pm, johnjbarton johnjbar...@johnjbarton.com wrote: On Oct 2, 4:00 pm, Steven Roussey srous...@gmail.com wrote: Something happen to break on error in svn? The option seems to have disappeared.. The short answer: use the pause button || on the Console now. The long version: It just moved to the Console panel. This is part of our overall Break On Anything! for 1.5. Console || == Break on Next Error Errors in the console: break on specific lines with errors. HTML || == Break on Next Mutate Element in the console: break on mutation to specific elements Script || == Break on Next JS statement Source line: break on next execution of this line DOM || == Break on next property update (maybe) DOM panel row: break on property change CSS || == Break on any style change CSS selector: break on selector changed CSS rule: break on rule changed. In addition: all the different kinds of break points will be listed in the Breakpoints side panel; as far as possible they will all support conditional expressions; the new breakpoint notification will report the reason/condition of the break. jjb --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~--~~~~--~~--~--~---
Re: Firebug debugging is not working
On Oct 9, 1:26 pm, James Calfee jslim...@gmail.com wrote: I'm using Firefox 3.0.12 on Windows and Firebug 1.4.3 When I set and exercise a break point nothing happens. I was so sure it is user error that I watched the Firebug video and used this exact example in the video: Went to getfirebug.com. Set a breakpoint in the onClickTab method on this line: if (img.className == topTab) Next, I clicked on a tab. The tab worked like in the video. I allowed Javascript in my NoScript 1.9 add-on, however, firebug did not do anything. There is nothing in the Error Console. Does anyone have any ideas? I suggest you try installing Firebug in a new Firefox profile and when that works, try adding other extensions until it breaks. http://groups.google.com/group/firebug/web/faq-about-firebug jjb Thanks, jc --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~--~~~~--~~--~--~---
Re: Extending firebug: Understanding Firebug.chrome.$(id) vs. FirebugChrome.$(id) vs $(id)
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 elements. jjb --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~--~~~~--~~--~--~---
Re: Extending firebug: Understanding Firebug.chrome.$(id) vs. FirebugChrome.$(id) vs $(id)
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)
{
FBTrace.sysout(lib.$ document: +(doc?
doc.location:document.location) + for ID: + id);
if (doc)
return doc.getElementById(id);
else
return document.getElementById(id);
};
When attached to the browser chrome I see this:
FTS0: chrome.$ document: chrome://browser/content/browser.xul for ID:
adfvLocationToolbar_logfiles and $ is: function (id, doc) {
FBTrace.sysout(lib.$ document: + (doc ? doc.location :
document.location) + for ID: + id);
if (doc) {
return doc.getElementById(id);
} else {
return document.getElementById(id);
}
}
FTS0: lib.$ document: chrome://browser/content/browser.xul for ID:
adfvLocationToolbar_logfiles
After attaching to a new window, I get this:
FTS0: chrome.$ document: chrome://firebug/content/firebug.xul for ID:
fbAdfvTypeMenu and $ is: function $(id, doc) {
if (doc) {
return doc.getElementById(id);
} else {
return document.getElementById(id);
}
}
As you can see, the global function $ from chrome's point of view is
a different function when firebug is in a window compared to when it
was attached to the browser.
I'll have to see if I can trace where on earth that new '$' is coming
from, because I do not see it in my code or your code at the moment,
but it does look like the firebug $ definition, just not the one from
lib.js that I am expecting.
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to
firebug+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~--~~~~--~~--~--~---
Firebug 1.5a26
http://blog.getfirebug.com/2009/10/09/firebug-1-5a26/ The last alpha for 1.5 is out. jjb --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~--~~~~--~~--~--~---
Re: Extending firebug: Understanding Firebug.chrome.$(id) vs. FirebugChrome.$(id) vs $(id)
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 $
in chrome.js.
I changed the $ function in chrome.$ to this:
$: function(id)
{
FBTrace.sysout(chrome.$ document: +(document.location) + for ID:
+ id + and $ is: + $ + FBL.$ = + FBL.$);
return $(id);
},
And $ in lib.js to this:
this.$ = function(id, doc)
{
FBTrace.sysout(lib.$ document: +(doc?
doc.location:document.location) + for ID: + id);
if (doc)
return doc.getElementById(id);
else
return document.getElementById(id);
};
But when I have firebug in its own window I see this output in the
console:
FTS0: chrome.$ document: chrome://firebug/content/firebug.xul for ID:
fbAdfvTypeMenu and $ is: function $(id, doc) {
if (doc) {
return doc.getElementById(id);
} else {
return document.getElementById(id);
}
} FBL.$ = function (id, doc) {
FBTrace.sysout(lib.$ document: + (doc ? doc.location :
document.location) + for ID: + id);
if (doc) {
return doc.getElementById(id);
} else {
return document.getElementById(id);
}
}
As you can see, the global $ function is different than FBL.$
function. I tried disabling all my extensions except for firebug and
mine, and so far I do not see who is overwriting the $ in chrome's
namespace or window object. Quite odd. Don't suppose you know what is
going on?
If it matters, I am using firefox 3.5.3 shipped by Ubuntu in Jaunty
and Firebug 1.4.3
Thanks for all your help.
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to
firebug+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~--~~~~--~~--~--~---
Re: Extending firebug: Understanding Firebug.chrome.$(id) vs. FirebugChrome.$(id) vs $(id)
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
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 firebug@googlegroups.com
To unsubscribe from this group, send email to
firebug+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~--~~~~--~~--~--~---
Re: Extending firebug: Understanding Firebug.chrome.$(id) vs. FirebugChrome.$(id) vs $(id)
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 same
as FBL.$, but when I open firebug in a window, I get a different $
in chrome.js.
I changed the $ function in chrome.$ to this:
$: function(id)
{
FBTrace.sysout(chrome.$ document: +(document.location) + for ID:
+ id + and $ is: + $ + FBL.$ = + FBL.$);
return $(id);
},
And $ in lib.js to this:
this.$ = function(id, doc)
{
FBTrace.sysout(lib.$ document: +(doc?
doc.location:document.location) + for ID: + id);
if (doc)
return doc.getElementById(id);
else
return document.getElementById(id);
};
But when I have firebug in its own window I see this output in the
console:
FTS0: chrome.$ document: chrome://firebug/content/firebug.xul for ID:
fbAdfvTypeMenu and $ is: function $(id, doc) {
if (doc) {
return doc.getElementById(id);
} else {
return document.getElementById(id);
}} FBL.$ = function (id, doc) {
FBTrace.sysout(lib.$ document: + (doc ? doc.location :
document.location) + for ID: + id);
if (doc) {
return doc.getElementById(id);
} else {
return document.getElementById(id);
}
}
As you can see, the global $ function is different than FBL.$
function. I tried disabling all my extensions except for firebug and
mine, and so far I do not see who is overwriting the $ in chrome's
namespace or window object. Quite odd. Don't suppose you know what is
going on?
I think these are the same function being accessed two different ways.
At the top of chrome.js you will see
(function() { with (fbXPCOMUtils) {
and at the top of lib.js:
var FBL = fbXPCOMUtils;
So all of the functions defined in lib.js are global functions in
chrome.js. This is generally true through out firebug source. The
only reason we use FBL.foo() is if we are in an event handler called
by something in Firefox that does not include our lib.js scope.
So $ in chrome.js resolves to a global from the with(fbXPCOMUtils)
and FBL.$ resolves to the same method as a property of FBL.
jjb
--~--~-~--~~~---~--~~
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 unsubscribe from this group, send email to
firebug+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~--~~~~--~~--~--~---
Re: Extending firebug: Understanding Firebug.chrome.$(id) vs. FirebugChrome.$(id) vs $(id)
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: 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 firebug@googlegroups.com
To unsubscribe from this group, send email to
firebug+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~--~~~~--~~--~--~---
Re: Something happen to break on error in svn?
If you hit pause on the script panel and reload I think it should break on the first JS statement in the page. I just want it to break on error. The menu item would persist across page loads, but I can't figure out how to do that now. That's all. --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~--~~~~--~~--~--~---
