Web Images Videos Maps News Shopping Gmail more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Group info
Members: 5213
Language: English
Group categories:
Computers > Software
More group info »
Recent pages and files
faq-about-firebug    

Firebug Frequently Asked Questions

Please see our new wiki based FAQ.


Older content:

Firebug Web Development Evolved  getfirebug.com releases FAQ Working Group Blog Bugs

  • Please give the version number for Firebug and Firefox when discussing issues.
  • Firebug 1.5 will work with Firefox 3.5 and Firefox 3.6
  • Firebug 1.4 works with Firefox 3.0 and Firefox 3.5
  • Firebug 1.3 works with Firefox 3.0 and Firefox 2.0
  • Firebug Lite works with IE, Safari, and Opera

Installing Firebug

Firebug Versions

  • Version 1.05: check using Firefox->Tools->Addons->Firebug. Version number on the panel.
  • Version 1.1: check using Firebug->BugMenu->About
  • Version 1.2+: hover on the Firefox status bar icon for Firebug

Installation Issues, Firefox 2.0

  • To enable Talkback: reinstall Firefox using "custom" install and select Talkback and DOM Inspector.

Installation Issues, Firefox 3.0

  • Firebug 1.0 is incompatible with Firefox 3.0.  Firebug 1.1 does not work completely.
  • Firebug 1.2 works on Firefox 3
  • Firebug 1.3 works with Firefox 3.0
  • Firebug 1.4 works with Firefox 3.5
  • Firebug 1.5 will target Firefox 3.6. 

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:
  • Exit Firefox
  • Get to a command line
    • Windows: Start->Run->"cmd" enter
    • Linux: you know how ;-)
  • Run Firefox with -ProfileManager
    • Windows: C:\\Program Files\\Mozilla Firefox\\firefox.exe -ProfileManager
  • Create New profile
  • Start Firefox with your new profile
  • Load Firebug into this clean profile.
  • Learn more about the Firefox Profile Manager 

Using the Tracing Version of Firebug (eg 1.4X rather then 1.4)

  • First follow the instructions from the preceding section to create a new Firefox profile. Install the tracing version.
  • Open Firebug, then open the tracing panel from the Firebug Icon menu (upper left in Firebug)
  • In the Tracing window Option tab, set ERRORS on, switch to the Log tab.
  • Try your problem page/function.
  • Look for error messages in the log. You can export the trace with the button at the top.
  • To get help, open an issue report and attach the trace.
  • 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".

Firebug bugs

  • Report bugs on the issues list: http://code.google.com/p/fbug/issues/list

    • Please be realistic when adding an issue.
    • Provide a small example script or page.
    • 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.

  • How to contribute a translation:

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.


See some screenshots of the activation UI here.

Version: 
Latest 3 messages about this page (4 total) - view full discussion
Dec 24 2007 by John J Barton
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.
Dec 24 2007 by pd
Hi John

This post:

http://groups.google.com/group/firebug/browse_thread/thread/dedbc313b2e26baf/dfcf100076db539d?lnk=gst&q=ff2+crashes#dfcf100076db539d

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.
1 more message »
Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google