Installing in a clean Profile (To test for interactions with other extensions)
Firefox and Firebug re-install rarely fixes problems because the configuration files are not altered on reinstall. To clear out the configuration files you need to create a new Firefox profile:
For problems with breakpoints, set UI_LOOP and BP, and SOURCEFILES
For problems with Console, set CONSOLE and ACTIVATION
For problems where Firebug UI is acting, set DISPATCH, ACTIVATION, and PANELS
Crashes, Firefox 3
Crash means the Firefox program ends and the crash report dialog box appears.
A Firefox crash is always a Firefox bug and needs to be reported to http://bugzilla.mozilla.org.
The crash information is available after you let the crash reporter log to to mozilla. You can read the report by using "about:crashes" as a URL in a reopened Firefox. This link should be supplied in any bug report; it sometimes takes several minutes for the server to digest the incoming reports.
You can optionally open a bug report for Firebug, http://code.google.com/p/fbug/issues/list but we cannot fix Firefox crashes. This is true even if the crash only happens when Firebug is enabled.
Crashes, Firefox 2.0
Crash means Firefox exits.
Please put "Firebug <your Firebug version>" in the Talkback comment field. If Talkback does not come up, see Installation Issues on this page.
Check about:config. If you have javascript.options.strict true, try setting it false.
All crashes are Firefox bugs, all Firebug can do is try to avoid using features that tend to crash.
Is it possible there is a mexican stand off scenario going on whereby Firebug developers say it's Firefox's problems, and then vice versa? If so something needs to be done to address this stand off.
There is no such standoff. No one working on Firefox claims that the FF2 crashes are caused by errors in Firebug code.
Please see https://bugzilla.mozilla.org/show_bug.cgi?id=400618
If diligent documenting of talkback incidents and corresponding bugzilla entries is needed, I'd like to help. Any thoughts?
More talkback traces would probably not help at this point.
The best way to help would be to create test cases that crashes in the
shortest possible wall-clock time. That will help developers pinpoint
the problem.
Use the Mozilla talkback site to look for your Firefox stack trace by searching on Comment "firebug".
Provide detailed step-by-step instructions on how to reproduce the problem.
Remember this is an open source project: the time you invest in explaining a bug goes a long ways toward getting it fixed. Conversely, incomplete instructions without an example will probably be a waste of your time: no one will know what to do with the report and it will be ignored.
Check that you have the issue "starred" so you receive email when your translation goes in or when other folks offer suggestions.
Enable Firebug 1.05 for Specific Sites
To enable Firebug only for some sites you are working on do this:
Disable Firebug:
Firefox->StatusBar->(green check or gray dot)->RightClick->Disable Firebug checked
Navigate Firefox to the site you want to work on.
Enable Firebug for Site:
Firefox->StatusBar-(Firefox->StatusBar->(green check or gray dot)->RightClick->Disable Firebug checkedDisable Firebug for ... unchecked.
To get finer control you can use
Firefox->StatusBar->(green check or gray dot)->RightClick->Allowed Sites
OR Firebug->BugIcon->AllowedSites
How to Enable/Disable Firebug 1.2
The logic behind enabling and disabling Firebug has been changed in 1.2. Since this version, every panel that could have negative impact on Firefox performance can be enabled and disabled separately. Thus there is no need to disable entire Firebug.
The following panels are activable. Notice that all these panels are disabled by default.
Console - Firebug's JavaScript Console
Script - JavaScript Debugger
Net - Network Monitor
A new activation menu has been introduced to make easy to enable/disable appropriate panel. This menu is located directly on the panel's tab (there is a little drop-down next to the tab label).
This menu can be used to enable/disable specific Firebug panel for:
the current site (e.g. the Enable debugger for www.google.com menu-item)
all sites (e.g. the Enable debugger menu-item)
Also, if a panel is disabled, its content is replaced by a form that allows one-click activation of multiple panels - for the current site - at once.
Sure, thanks. Its a bit long so it would be great if it can be at the
bottom and referenced from above. I don't want bog down people looking
for info with a long novel on FF2.
Seems very helpful. Perhaps it should be added to this FAQ or even a
separate FAQ page?
I'm happy to do the copy/paste work if you like.
Dec 8 2007 by John J Barton
Since you addition to the FAQ is speculation I don't think its a
useful addition. This list would be, in my opinion, a much more
effective and helpful place to discuss issues that are uncertain. FAQ
should be about answers rather than questions.