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

+

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 [https://bugzilla.mozilla.org/ report it to Mozilla].

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].

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 [[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 ===

Line 49:

Line 49:

** 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:

-

# Create a new profile, install Firebug, reproduce the problem. Still a bug? Report the problem, else

+

# Open the [https://developer.mozilla.org/en-US/docs/Error_Console Firefox Error Console] (<code class="key">Ctrl</code>/<code class="key">&#8984;</code>+<code class="key">Shift</code>+<code class="key">J</code>). Any errors related to Firebug? Copy them and remember to include them in your report.

# 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 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), 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)

-

# Use <code>about:addons</code> or ''Firefox > Tools > Addons'' to disable all addons except Firebug. Solved? 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:

-

* Make sure your problem 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,

+

* 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

** 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 have additional info, add a comment to it and attach your test case, if there isn't one yet, else

Revision as of 07:32, 14 January 2014

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.

Install problems: 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:

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)