I found a Firebug Bug!

From FirebugWiki

(Difference between revisions)
Jump to: navigation, search
m (Changed links to Fixed issues in 1.7 and 1.8)
(Fixed links)
Line 12: Line 12:
== The quickest way to stop having the problem ==
== The quickest way to stop having the problem ==
-
# Does Firebug Install? No: [http://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug!#Install_problems:_Contact_Firefox_Support Contact Firefox support].
+
# Does Firebug Install? No: [[#Install problems: Contact Firefox Support|Contact Firefox support]].
-
# Does Firebug Open? No: [http://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug!#Cannot_Open_or_Mysterious_Problems:_Create_a_New_Firefox_Profile Create a new Firefox profile].
+
# Does Firebug Open? No: [[#Cannot Open or Mysterious Problems: Create a New Firefox Profile|Create a new Firefox profile]].
-
# Is the Firebug user interface partly blank, or not responding? Yes: [http://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug!#Partial_User_Interface_Failures:_Disable_Other_Extensions Fix other extensions].
+
# Is the Firebug user interface partly blank, or not responding? Yes: [[#Partial User Interface Failures: Disable Other Extensions|Fix other extensions]].
-
# Is Firebug doing things you don't want? Yes: [http://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug!#Firebug_Not_Acting_Like_You_Remember:_Reset_All_Firebug_Options Reset the options].
+
# Is Firebug doing things you don't want? Yes: [[#Firebug Not Acting Like You Remember: Reset All Firebug Options|Reset the options]].
=== Install problems: Contact Firefox Support ===
=== Install problems: Contact Firefox Support ===
Line 25: Line 25:
* no bookmarks, and
* no bookmarks, and
* no options from your current configuration.
* no options from your current configuration.
-
If you need help, please read [[FAQ#Installing_in_a_clean_profile|how to create a clean profile]]
+
If you need help, please read [[FAQ#Installing in a clean profile|how to create a clean profile]]
=== Partial user interface failures: Disable other extensions ===
=== Partial user interface failures: Disable other extensions ===
Line 54: Line 54:
# Create a new profile, install Firebug, reproduce the problem. Still a bug? Report the problem, else
# Create a new profile, install Firebug, reproduce the problem. Still a bug? Report the problem, else
# Return to your previous profile, open the URL <code>about:config</code>, type <code>extensions.firebug</code>, save the result in a text file, reset all options, reproduce the problem. Solved? Then report the problem using the list of settings, else
# Return to your previous profile, open the URL <code>about:config</code>, type <code>extensions.firebug</code>, save the result in a text file, reset all options, reproduce the problem. Solved? Then report the problem using the list of settings, else
-
# Use "about:addons" or Firefox > Tools > Addons to disable all addons except Firebug. Solved? Then enable the other extensions one by one until you find the buggy one and report it.
+
# Use <code>about:addons</code> or Firefox > Tools > Addons to disable all addons except Firebug. Solved? Then enable the other extensions one by one until you find the buggy one and report it.
=== Reporting the problem ===
=== Reporting the problem ===
Now that you know, that it is a Firebug problem:
Now that you know, that it is a Firebug problem:
-
* If your steps to reproduce the problem involve public data: [http://code.google.com/p/fbug/issues/list?can=2&q=&sort=-id Open a bug report].
+
* If your steps to reproduce the problem involve public data: [http://code.google.com/p/fbug/issues/list?can=1&sort=-id Open a bug report].
* If your steps to reproduce do not involve public data:
* If your steps to reproduce do not involve public data:
** develop a test case, that can be public, or
** develop a test case, that can be public, or
-
** [http://code.google.com/p/fbug/issues/list?can=2&q=&sort=-id open a bug report] and attach [[FBTrace]] tracing data.
+
** [http://code.google.com/p/fbug/issues/list?can=1&sort=-id open a bug report] and attach [[FBTrace]] tracing data.
If you can't give a test case, please ask in the [http://groups.google.com/group/firebug Firebug Google Group] or in the [irc://irc.mozilla.org/firebug Firebug IRC channel].
If you can't give a test case, please ask in the [http://groups.google.com/group/firebug Firebug Google Group] or in the [irc://irc.mozilla.org/firebug Firebug IRC channel].
== See also ==
== See also ==
-
* [http://code.google.com/p/fbug/issues/list?can=2&q=label%3ATest-case-available Our Top Priority Bugs]
+
* [http://code.google.com/p/fbug/issues/list?can=1&q=label%3ATest-case-available Our Top Priority Bugs]
* [http://code.google.com/p/fbug/issues/list?can=1&q=label%3Afixed1.7a1%2Cfixed1.7a2%2Cfixed1.7a3%2Cfixed1.7a4%2Cfixed1.7a5%2Cfixed1.7a6%2Cfixed1.7a7%2Cfixed1.7a8%2Cfixed1.7a9%2Cfixed1.7a10%2Cfixed1.7a11%2Cfixed1.7b1%2Cfixed1.7b2%2Cfixed1.7b3%2Cfixed1.7.1b1%2Cfixed1.7.1b2%2Cfixed1.7.1b3%2Cfixed1.7.2%2Cfixed1.7.3 Fixed issues in Firebug 1.7]
* [http://code.google.com/p/fbug/issues/list?can=1&q=label%3Afixed1.7a1%2Cfixed1.7a2%2Cfixed1.7a3%2Cfixed1.7a4%2Cfixed1.7a5%2Cfixed1.7a6%2Cfixed1.7a7%2Cfixed1.7a8%2Cfixed1.7a9%2Cfixed1.7a10%2Cfixed1.7a11%2Cfixed1.7b1%2Cfixed1.7b2%2Cfixed1.7b3%2Cfixed1.7.1b1%2Cfixed1.7.1b2%2Cfixed1.7.1b3%2Cfixed1.7.2%2Cfixed1.7.3 Fixed issues in Firebug 1.7]
* [http://code.google.com/p/fbug/issues/list?can=1&q=label%3Afixed1.8a1%2Cfixed1.8a2%2Cfixed1.8a3%2Cfixed1.8b1%2Cfixed1.8b2%2Cfixed1.8b3%2Cfixed1.8b4%2Cfixed1.8b5 Fixed issues in Firebug 1.8]
* [http://code.google.com/p/fbug/issues/list?can=1&q=label%3Afixed1.8a1%2Cfixed1.8a2%2Cfixed1.8a3%2Cfixed1.8b1%2Cfixed1.8b2%2Cfixed1.8b3%2Cfixed1.8b4%2Cfixed1.8b5 Fixed issues in Firebug 1.8]

Revision as of 07:45, 25 July 2011

Every Firebug release goes through regression testing and community testing by alpha and beta users. In addition we use Firebug code to develop Firebug.

Obvious and glaring "bugs" in Firebug are very often not things, that Firebug can fix. Rather they are problems caused by other extensions, by unusual settings, or by bugs in Firefox. This page attempts to help you determine, if your problem really is a Firebug bug or it is something else you can fix.

Please note: It is not possible for Firebug to crash Firefox. If Firefox crashes, it's a Firefox bug. However, unless you are running a nightly build of Firefox, creating a new Firefox profile and installing Firebug will fix it.

Before you start make sure your Firefox extensions are all updated.

If you have a problem with Firebug, first decide:

  • Do you want the quickest way to stop having the problem? or
  • Do you want to understand the problem so it can be fixed?

Contents

The quickest way to stop having the problem

  1. Does Firebug Install? No: Contact Firefox support.
  2. Does Firebug Open? No: Create a new Firefox profile.
  3. Is the Firebug user interface partly blank, or not responding? Yes: Fix other extensions.
  4. Is Firebug doing things you don't want? Yes: Reset the options.

Install problems: Contact Firefox Support

For all issues with installation contact Firefox support.

Cannot open or mysterious problems: Create a new Firefox profile

Creating a new Firefox profile is a highly reliable way to solve problems. Note: uninstalling and reinstalling of Firebug or Firefox very rarely helps, because preferences won't get deleted. A new Firefox profile is a clean configuration with:

  • no addons,
  • no bookmarks, and
  • no options from your current configuration.

If you need help, please read how to create a clean profile

Partial user interface failures: Disable other extensions

Firebug touches a lot of the Firefox platform and the action of other extensions while Firebug operates can interfere with Firebug's work.

  1. Firefox > Tools > Addons or URL about:addons
  2. For every extension select "disable"
  3. Restart Firefox

If Firebug works, then one of the disabled extensions interfere with Firebug. You can try to enable them a few at a time to work out which one interferes.

Firebug not acting like you remember: Reset all Firebug options

Firebug > Firebug Icon Menu (upper left corner) > Options > Reset All

To understand the problem so it can be fixed

  1. Reproduce the problem
  2. Isolate the problem
  3. Report the problem

Reproducing the problem

  • To understand a problem you need to be able to reproduce it.
  • To get the problem fixed you need to communicate the procedure to reproduce the problem.
  • So the first and most critical step in fixing a problem is to reproduce it:
    • Find a sequence of steps that you can perform to show the problem when you first open Firefox.
    • Write the steps down so you can remember them and repeat them.

Isolating the problem

Now that you can reproduce the problem, figure out who to blame:

  1. Create a new profile, install Firebug, reproduce the problem. Still a bug? Report the problem, else
  2. Return to your previous profile, open the URL about:config, type extensions.firebug, save the result in a text file, reset all options, reproduce the problem. Solved? Then report the problem using the list of settings, else
  3. Use about:addons or Firefox > Tools > Addons to disable all addons except Firebug. Solved? Then enable the other extensions one by one until you find the buggy one and report it.

Reporting the problem

Now that you know, that it is a Firebug problem:

  • If your steps to reproduce do not involve public data:

If you can't give a test case, please ask in the Firebug Google Group or in the Firebug IRC channel.

See also

Personal tools