Archive for May, 2010

Firebug Lite 1.3.0

Monday, May 24th, 2010

Pedro Simonetti Garcia announces the release of Firebug Lite 1.3.0!  This in-page version of the Firebug concept offers many of the Firebug features popular in Firebug for Firefox, but it works in many browsers.  The  new release improves the user interface, deepens the implementation of CSS support, and improves the inspector and console panel.

With 1.3 Pedro Simonetti began integrating the Firebug Lite and Firebug for Firefox source code.  Next we divide Firebug for Firefox into user-interface (front end) and information extraction (back end). Then we merge Firebug Lite and the new front end. That gives us a common front end interface for Firefox multi-process, Fennec mobile web, Firefox with JSDebugv2, and cross browser. So in one master stroke Pedro Simonetti enhances Firebug Lite and sets us on a new course for Firebug development!

Of course the Firefox version of Firebug has many more features and we keep moving it forward. Ultimately we hope this trend continues: Firebug gets stronger on all browsers but the Firefox version keeps pushing out ahead.


Please followup in the newsgroup.

Firebug 1.6a11

Friday, May 21st, 2010 has Firebug 1.6X.0a11. This release is dedicated to Sebastian Zartner who recently joined the Firebug Working Group and has been working on our bug list.

  • Honza implemented console.table so source like this:
  • var family = {};
    family.header = ["First", "Last", "Age", "Desc"];
    family.mother = new Person("Susan", "Doyle", 32);
    family.father = new Person("John", "Doyle", 33);
    family.daughter = new Person("Lily", "Doyle", 5);
    family.son = new Person("Mike", "Doyle", 8);
    family.mother.desc = "mother";
    family.father.desc = "father";


    More examples are available in our console/api/table test page. This feature was suggested by Patrick Mueller who works on webkit based on a similar feature implemented in FirePHP by Christoph Dorn.

  • Disabling break on next error and  debugger; keywords. When you hit these in the debugger you now have the option of replacing them with a disabled breakpoint. The debugger will not break at these lines until you remove the disabled breakpoint:
  • You can also see the forward and back arrows Honza added in 1.6a10 in these screenshots.

Of course we have bug fixes, mostly around problems I created with the persistent breakpoints feature.


Please post comments in the newsgroup.

Firebug 1.5.4 on AMO

Thursday, May 6th, 2010

Firebug 1.5.4 has been available on for a while and since we have received only positive feedback, it’s now available on too.

This minor update fixes two annoying bugs. One is related to script truncation problem and the other to an options menu (the mini drop down menu available for the selected panel tab).

Special thanks to Mark Rawling for providing test cases and help!


Please followup in the newsgroup.

Firebug at Velocity 2010 Santa Clara, CA June 23

Monday, May 3rd, 2010

We’ll be showing a quick Firebug demo at Velocity again this year. We are on Wed. morning June 23.  I’ll try to highlight a couple of new things from the Net panel and the new breakpoints, using break on XHR for the example.

Lightning Demos Andreas Grabner (dynaTrace Software), John J. Barton (IBM), Stoyan Stefanov (Yahoo! Inc), Bryan McQuade (Google).

The promoter says you can put the code vel10fsp in when you register to get 20% off.


Comments in the newsgroup please.

Dynamic and Graphical Web Page Breakpoints: Firebug at WWW2010

Monday, May 3rd, 2010

On Thursday Apr. 28 Jan Odvarko (Honza) and I presented our paper “Dynamic and Graphical Web Page Breakpoints” at WWW 2010 in Raleigh, North Carolina, USA. These features were implemented in Firebug 1.2 through 1.5.  The HTML slides + demo we presented are now on-line.

Our talk went smoothly, with Honza explaining the demos while I went over the motivation, implementation, and related work. We had all positive comments and questions.

In discussions after the talk we kicked around the idea of a “Browser Research and Development” workshop. Browser researchers would present ideas and prototypes; browser developers would present ideas and problems. The focus would be on getting more browser research published and implemented while also stimulating more research in areas with the most potential impact on browsers. Most browser researchers want to have practical impact; the pace of innovation  in browsers demands more usable research efforts.  The WWW2010 venue is fine for final presentations, but it’s not a place where research and development meet. Let me know if you have interest in  such an event.


Please post comments on the newsgroup.