I found a Firebug Bug!

From FirebugWiki

(Difference between revisions)
Jump to: navigation, search
(The quickest way to stop having the problem)
m (Fixed link to how to create a new profile)
(37 intermediate revisions not shown)
Line 1: Line 1:
Every Firebug release goes through [http://getfirebug.com/testresults regression testing] and community testing by alpha and beta users. In addition we use Firebug code to develop Firebug.   
Every Firebug release goes through [http://getfirebug.com/testresults 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.
+
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, if it is something else you can fix by your own, or something that somebody else needs to fix.
-
Before you start, make sure your Firefox extensions are all updated.
+
Please note: '''Firebug is not responsible for Firefox crashes.''' 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 probably fix it. If you want the crash fixed, please [https://bugzilla.mozilla.org/ report it to Mozilla].
 +
 
 +
Before you start make sure your Firefox extensions are all updated.
If you have a problem with Firebug, first decide:  
If you have a problem with Firebug, first decide:  
-
* Do you want the quickest way to stop having the problem, or
+
* Do you want the quickest way to stop having the problem? or
-
* Do you want to understand the problem so it can be fixed,
+
* Do you want to understand the problem so it can be fixed?
== 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: [#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: [#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: [#Firebug_Not_Acting_Like_You_Remember:_Reset_All_Firebug_Options reset 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 ===
-
For all issues with installation, contact Firefox support.
+
For all issues with installation contact [http://support.mozilla.com/en-US/kb/Unable%20to%20install%20add-ons?s=addon+install&as=s Firefox support].
-
=== Cannot Open or Mysterious Problems: Create a New Firefox Profile ===
+
=== Cannot open or mysterious problems: Create a new Firefox profile ===
-
Creating a new Firefox profile is a highly reliable way to solve problems. A new Firefox profile is a clean configuration with:  
+
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 addons,
-
* no bookmarks, and  
+
* no bookmarks, and
-
* no options from your current configuration  
+
* no options from your current configuration.
-
For help on creating a new profile see [[FAQ#Installing_in_a_clean_profile]]
+
If you need help, please read [[Install Firebug into a clean profile|how to create a clean profile]]
-
=== Partial User Interface Failures: Disable Other Extensions ===
+
=== 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.  
Firebug touches a lot of the Firefox platform and the action of other extensions while Firebug operates can interfere with Firebug's work.  
-
# Firefox > Tools > Addons or URL "about:addons"
+
# ''Firefox > Tools > Addons'' or URL <code>about:addons</code>
# For every extension select "disable"
# For every extension select "disable"
-
# restart Firefox.
+
# 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.  
+
If Firebug works, then one of the disabled extensions interferes 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 not acting like you remember: Reset all Firebug options ===
-
Firebug > Firebug Icon Menu (upper left corner) > Options > Reset All
+
''Firebug Icon Menu (upper left corner) > Options > Reset All Firebug Options''
== To understand the problem so it can be fixed ==
== To understand the problem so it can be fixed ==
Line 39: Line 41:
# Isolate the problem
# Isolate the problem
# Report the problem
# Report the problem
 +
=== Reproducing the problem ===
=== Reproducing the problem ===
-
*To understand a problem you need to be able to reproduce it;
+
* 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.  
+
* 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:  
+
* 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.  
+
** 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.
** Write the steps down so you can remember them and repeat them.
 +
 +
See also the information about [[Creating a Test Case|how to create a test case]].
=== Isolating the problem ===
=== Isolating the problem ===
Now that you can reproduce the problem, figure out who to blame:
Now that you can reproduce the problem, figure out who to blame:
 +
# Open the [https://developer.mozilla.org/en-US/docs/Error_Console Firefox Error Console] (<code class="key">Ctrl/&#8984;+Shift+J</code>). Any errors related to Firebug? Copy them and remember to include them in your report.
# 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 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
+
# Return to your previous profile, open the Add-ons Manager via ''Firefox menu bar > Tools > Add-ons'', ''Firefox button > Add-ons'' or <code>about:addons</code> to disable all extensions except Firebug. Solved? Enable the other extensions again one by one until you find the buggy one and report it, else
-
# Use "about:addons" or Firefox > Tools > Addons to disable all addons except Firebug. Solved? Then enable other extension until you find the buggy one and report it.
+
# Open the Troubleshooting Information via ''Firebug Button > Help > Troubleshooting Information'', click ''Open Containing Folder'', open <code>prefs.js</code> in a text editor, copy all lines containing <code>extensions.firebug</code> into a separate text file, reset all options (via ''Firebug Icon Menu (upper left corner) > Options > Reset All Firebug Options''), reproduce the problem. Solved? Report the problem attaching the created file, else
 +
# In the profile folder go to ''firebug/'', move the file ''breakpoints.json'' (if it doesn't exist, go to step 4) out of that folder, reproduce the problem. Solved? Report the problem attaching your ''breakpoints.json'' ('''Attention:''' ''breakpoints.json'' contains the URLs of all breakpoints you set, so make sure there's nothing, that shouldn't be public), else
 +
# In the profile folder under ''firebug/'' move the file ''annotations.json'' (if it doesn't exist, go to step 5) out of that folder, reproduce the problem. Solved? Report the problem attaching your ''annotations.json'' ('''Attention:''' ''annotations.json'' contains the URLs of all pages you enabled Firebug for, so make sure there's nothing, that shouldn't be public)
 +
 
=== Reporting the problem ===
=== Reporting the problem ===
-
Now that 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].
+
* Make sure your problem isn't listed in the [http://getfirebug.com/knownissues known issues] and isn't [http://code.google.com/p/fbug/issues/list?can=1&q=Type%3DDefect&sort=-id already reported]. If there is already an issue,
 +
** but it is closed already, go to the next step, else
 +
** if you have additional info, add a comment to it and attach your test case, if there isn't one yet, else
 +
 
 +
* If your steps to reproduce the problem involve public data: Follow the [[rules for the issue tracker]] and open [http://code.google.com/p/fbug/issues/list?can=1&sort=-id open a bug report], else
 +
 
 +
* If your steps to reproduce do not involve public data:
 +
** develop a [[Creating a Test Case|test case]], that can be public, or
 +
** [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 public test case, please ask in the [http://groups.google.com/group/firebug Firebug discussion group] or in the [irc://irc.mozilla.org/firebug Firebug IRC channel].
 +
 
 +
Also please do '''not''' post whole blocks of code into the issues. That just makes it hard to read them. Instead put it into a file and attach that file to the report.
-
If you steps to reproduce do not involve public data:
+
== See also ==
-
* develop a test case that can be public, or
+
* [http://code.google.com/p/fbug/issues/list?can=1&q=Type%3DDefect+Test%3Dcase-available%2Ccase-in-suite&sort=-stars&colspec=ID+Type+Status+Owner+Test+Summary+Stars Our top priority bugs]
-
* [http://code.google.com/p/fbug/issues/list?can=2&q=&sort=-id open a bug report] and attach [http://getfirebug.com/wiki/index.php/FAQ#Using_the_Tracing_Version_of_Firebug tracing data].
+
* [http://code.google.com/p/fbug/issues/list?can=1&q=Type%3DDefect+-is%3Aopen+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 bugs in Firebug 1.7]
 +
* [http://code.google.com/p/fbug/issues/list?can=1&q=Type%3DDefect+-is%3Aopen+label%3Afixed1.8a1%2Cfixed1.8a2%2Cfixed1.8a3%2Cfixed1.8b1%2Cfixed1.8b2%2Cfixed1.8b3%2Cfixed1.8b4%2Cfixed1.8b5+OR+fixed%3A1.8 Fixed bugs in Firebug 1.8]
 +
* [http://code.google.com/p/fbug/issues/list?can=1&q=Type%3DDefect+-is%3Aopen+fixed%3A1.9 Fixed bugs in Firebug 1.9]
 +
* [http://code.google.com/p/fbug/issues/list?can=1&q=Type%3DDefect+-is%3Aopen+fixed%3A1.10 Fixed bugs in Firebug 1.10]
 +
* [[I am missing a feature in Firebug!|Create an enhancement request]]
 +
* [[Firebug Terminology]]
 +
* [[March Of The Firebugs]]

Revision as of 12:31, 18 February 2013

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, if it is something else you can fix by your own, or something that somebody else needs to fix.

Please note: Firebug is not responsible for Firefox crashes. 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 probably fix it. If you want the crash fixed, please report it to Mozilla.

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 interferes 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 Icon Menu (upper left corner) > Options > Reset All Firebug Options

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.

See also the information about how to create a test case.

Isolating the problem

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

  1. Open the Firefox Error Console (Ctrl/⌘+Shift+J). Any errors related to Firebug? Copy them and remember to include them in your report.
  2. Create a new profile, install Firebug, reproduce the problem. Still a bug? Report the problem, else
  3. Return to your previous profile, open the Add-ons Manager via Firefox menu bar > Tools > Add-ons, Firefox button > Add-ons or about:addons to disable all extensions except Firebug. Solved? Enable the other extensions again one by one until you find the buggy one and report it, else
  4. Open the Troubleshooting Information via Firebug Button > Help > Troubleshooting Information, click Open Containing Folder, open prefs.js in a text editor, copy all lines containing extensions.firebug into a separate text file, reset all options (via Firebug Icon Menu (upper left corner) > Options > Reset All Firebug Options), reproduce the problem. Solved? Report the problem attaching the created file, else
  5. In the profile folder go to firebug/, move the file breakpoints.json (if it doesn't exist, go to step 4) out of that folder, reproduce the problem. Solved? Report the problem attaching your breakpoints.json (Attention: breakpoints.json contains the URLs of all breakpoints you set, so make sure there's nothing, that shouldn't be public), else
  6. In the profile folder under firebug/ move the file annotations.json (if it doesn't exist, go to step 5) out of that folder, reproduce the problem. Solved? Report the problem attaching your annotations.json (Attention: annotations.json contains the URLs of all pages you enabled Firebug for, so make sure there's nothing, that shouldn't be public)

Reporting the problem

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

  • Make sure your problem isn't listed in the known issues and isn't already reported. If there is already an issue,
    • but it is closed already, go to the next step, else
    • if you have additional info, add a comment to it and attach your test case, if there isn't one yet, else

If you can't give a public test case, please ask in the Firebug discussion group or in the Firebug IRC channel.

Also please do not post whole blocks of code into the issues. That just makes it hard to read them. Instead put it into a file and attach that file to the report.

See also

Personal tools