My favorites | Sign in
Project Home Wiki Issues
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 5190: 1.10a2 - Firebug.setPref is gone
1 person starred this issue and may be notified of changes. Back to list
Status:  ProbablyWorks
Closed:  Oct 2012

Sign in to add a comment
Reported by, Jan 29, 2012
I am working on a Firebug extension and have a XUL window which has the Firebug object. Somehow in 1.10a2 the setPref method is not available from the Firebug anymore.

Has this been moved? and where can we find it now? 


Best regards 


Mac OS X
Firefox 9.0.1
Firebug 1.10a2
Jan 31, 2012
The function should still be available using Firebug.Options.setPref(). Or, if you use the same modular structure as Firebug, you can put "firebug/lib/options" into the list of required modules.

Does that fix your problem?

Status: NeedInfo
Labels: api
Feb 1, 2012
No! Seems like I have another Firebug object in my browserOverlay
Sooner or later I am going to use the AMD structure.

What I have now is a browser overlay, embedding a JavaScript. 
When I trace the Firebug object from this script I no longer get the same Firebug object as I have in the extension (Firebug overlay).

See the screenshot for the trace result.

Screen Shot 2012-02-01 at 8.04.13 PM.png
86.5 KB   View   Download
Feb 2, 2012
Project Member #3
It could be that you are overlaying:

While you should overlay:

(see your chrome.manifest)

Is that the case?

Feb 2, 2012
Yes I am overlaying both browser/content/browser.xul and firebug/content/firebugOverlay.xul

In browser I basically have a XUL toolbar button which open a XUL window
I am opening the window using the method described here

Maybe I have misunderstood, but should also browser/XUL stuff go into the firebugOverlay ?

I am working on structuring the extension by browser and firebug

My chrome.manifest:

content		cms-server-trace-extension		chrome/content/ xpcnativewrappers=no

overlay		chrome://firebug/content/firebugOverlay.xul		chrome://cms-server-trace-extension/content/firebug-module/overlay.xul
overlay		chrome://browser/content/browser.xul		chrome://cms-server-trace-extension/content/browser/overlay.xul
skin        cms-server-trace-extension      classic/1.0 chrome/skin/classic/
resource    cms-server-trace-extension      chrome/content/
locale  cms-server-trace-extension  en-US   chrome/locale/en-US/


Feb 3, 2012
Project Member #5
Since 1.10, Firebug loaded is delayed till the user actually needs it. This means that at the begging, when overlays apply on browser.xul, the Firebug object has just minimal set of methods.

Your browser.xul overlay should append only global things to the browser UI, e.g. a toolbar button.

Your firebugOverlay.xul overlay should append things to the Firebug UI (panels, modules, etc). When this overlay is loaded Firebug object is what you expect. This means that load of this overlay is also delayed till the user actually opens Firebug UI.

Feb 4, 2012
Project Member #6
I see! Thanks for the explanation!

Anyway, I was trying the bootstrapped example in examples/firebug1.10/HelloBootAMD 
After building and installing successfully I can not see the Panel in Firebug and FBTrace does not log anything.
I also tried using a Firebug build based on branches/firebug.10.restartless without getting HelloBootAMD to do anything.

Is the HelloBootAMD in rev #12815 actually ment to work now?

Feb 4, 2012
Project Member #7
> Is the HelloBootAMD in rev #12815 actually ment to work now?
I think I see the problem

Does it work for you if you open Firebug UI, close and reopen it?


Feb 4, 2012
Project Member #8
I committed a patch for the problem I am seeing at R12816
Does it help for you?

Feb 4, 2012
Project Member #9
With R12816 I see the panel


Feb 6, 2012
Project Member #10
Ok! Thanks for the answers. I guess I'll figure out my XUL.

Just one more question about bootstrapped extensions ;)

Is it wise to start porting my old XUL based extension code to a bootstrapped version now? 
It is no fancy stuff. Just a module that adds a http request header upon the request, and appends a tab to a net request entry. I'll be working with the 1.10/trunk version of Firebug while doing this.

Feb 6, 2012
Project Member #11
> Is it wise to start porting my old XUL based extension code to
> a bootstrapped version now? 
All the bootstrapped stuff (including API for extensions) is pretty new so, there can be changes. But your feedback could be very valuable. So, I would be happy if you use it and provide feedback, but at the same time you should be ready for changes.

I am planning to provide some docs (this week) so, perhaps you could start next week.

Feb 7, 2012
Project Member #12
I've already started playing with the HelloBootAMD example as a warm up and can start the refactoring of my extension next week.

Where do you plan to publish the docs?


Feb 7, 2012
Project Member #13
Somewhere on

I'll post a link here

Apr 30, 2012
I guess Honza just missed to post the link. Here it is:

Also the following site might be of interest when migrating your extension:

Is this issue solved now? I.e. can we close it?

May 1, 2012
Project Member #15
Thanks for the links Sebastian!
Jul 20, 2012
Project Member #16
Thomas, any update?

Oct 22, 2012
Project Member #17
Since there was no feedback anymore, I assume I can close this issue now.

Status: ProbablyWorks
Sign in to add a comment

Powered by Google Project Hosting