blog
discuss
releases
documentation

Development Blog

Firebug 2.0 beta 1

getfirebug.com has Firebug 2.0 beta 1

Firebug 2.0b1 fixes 13 issues
Firebug 2.0b1 is compatible with Firefox 30-31

 

The feedback we have got for Firebug 2 so far has been positive, some issues reported and fixed. We feel strong and in order to get more feedback we decided to move forward and start beta phase. Beta releases will also be uploaded on AMO to update the beta channel.

Highlights from this release

One little improvement made it into this release. If you deal with Cookies you can now export all cookies for the current page using new Export as JSON to Clipboard action (issue 7197).

In order to have this action available you need to set the following preference to true: extensions.firebug.cookies.jsonClipboardExport
(use about:config)

 


 

One useful concept improved in Firebug 2 is related to JavaScript errors and the debugger. Thanks to JSD2 API Firebug could finally implement it correctly. So, let’s take a look at four scenarios that explains how you can identify JS errors in your code and fix it.

Break On Next Error

This feature is part of Break On … concept in Firebug. This time we are interested in Break On Next Error related to the Console panel.

This features allows to break on an error that happens next. It’s useful in cases where the user knows when the error happens.

The use case is (try live example):

  • Open Firebug and enable the Console and Script panel
  • Switch to the Console panel and click Break On All Errors
  • Operate your page to cause JS error
  • Firebug should switch to the Script panel and break in the debugger
    at the line where the error happened

Error Breakpoint

In this case Firebug integrates JS errors an breakpoints within the Console panel.

This features allows to break on particular error that the user created a breakpoint for.

The use case is (try live example):

  • Open Firebug and enable the Console and Script panel
  • Operate your page to cause an error
  • You should see an error log in the Console panel allowing to set a breakpoint on it
  • Operate your page to cause the same error
  • Firebug should switch to the Script panel and break in the debugger
    at the line where the error happened

Break On Exceptions

In this case we move into the Script panel and use one of its options.

This feature allows to break on any exception that happens in your app. It works as an option and you don’t need to reactivate it after it happens.

The use case is (try live example):

  • Open Firebug and enable the Script panel
  • Switch to the Script panel and check Break On Exceptions option in the panel tab options menu
  • Operate your page to cause an exception
  • Firebug should switch to the Script panel and break in the debugger
    at the line where the error happened

Ignore Caught Exceptions

This case is an extension of the previous one. In some cases the user is only interested in uncaught exceptions since the others are caught and known.

This features allows to break on any exception that happens and is *not* caught by catch clause. It works as an option you don’t need to reactivate it.

The use case is (try live example):

  • Open Firebug and enable the Script panel
  • Switch to the Script panel and check Break On Exceptions and Ignore Caught Exceptions option in the panel tab options menu
  • Operate your page to cause uncaught exception
  • Firebug should switch to the Script panel and break in the debugger
    at the line where the error happened

Please post feedback in the newsgroup, thanks.

Jan ‘Honza’ Odvarko

 

Comments are closed.