Comments on: Firebug Features Poll part 2 – The Unloved

By: Andy

Andy — Fri, 23 Oct 2009 16:51:29 +0000

I literally would not be able to do my job if it were not for the CSS panel in Firebug.

By: robcee

robcee — Thu, 22 Oct 2009 23:39:11 +0000

Jesse, people do use the CSS panel as a few commenters here mentioned. I wouldn’t mind having a validation extension for Firebug though.

Definitely agree chrome errors should probably be shut off by default. I’ll check into that.

Thanks for the comments!

By: Jesse Ruderman

Jesse Ruderman — Thu, 22 Oct 2009 21:35:59 +0000

“[Console noise] can often be cut down by unchecking the “Show Chrome Errors” and messages options in the Console’s mini-menu.”

The default probably shouldn’t include chrome errors. Maybe it should be a tab/toggle between chrome and content, rather than a toggle between “include chrome errors” and “don’t include chrome errors”.

By: Jesse Ruderman

Jesse Ruderman — Thu, 22 Oct 2009 21:33:42 +0000

“Using [the CSS panel] as a validation tool seems to be one of the only uses for it, so maybe reworking it to do that job better would be an improvement.”

So maybe it could be replaced by a “Validation” panel that includes HTML validation and JS linting?

By: Encuesta Sobre Caracterísitas de Firebug ~ Parte 2 « Notas de un Peregrino

Encuesta Sobre Caracterísitas de Firebug ~ Parte 2 « Notas de un Peregrino — Thu, 22 Oct 2009 02:43:22 +0000

[...] siguiente es una traducción de un post de Rob Campbell (Aquí está el original), uno de los desarrolladores de [...]

By: Mark T.

Mark T. — Wed, 21 Oct 2009 21:08:53 +0000

I don’t use the script debugger often, but when I need to, it saves a tremendous amount of time versus sprinkling log statements throughout my code and guessing where things may be broken.

The stability of the debugger and breakpoint accuracy was substantially improved from whatever earlier version I was using to Firebug 1.4.3 today. Sincerely, awesome work on improving the debugger!

By: Praveen

Praveen — Wed, 21 Oct 2009 07:41:21 +0000

I love the “Call Stack” tab and “Break on All Errors” option. Debugging in Firebug has gotten better!

By: Wes

Wes — Tue, 20 Oct 2009 17:29:04 +0000

I’m a fan of the DOM panel. Very useful to me when I was learning how ExtJS worked. It was nice to be able to follow the tree down and learn about the structure of things.

The console is invaluable in debugging scripts to me and my coworkers, so don’t listen to the guys who knock it.

By: MarkC

MarkC — Tue, 20 Oct 2009 16:04:15 +0000

Unfortunately there don’t really seem to be any tools that work reliably with _remote_ XUL. Venkman won’t debug our app. Firebug won’t debug our app. Chromebug crashed my browser when I tried it a few days ago, to the extent that I had to manually remove the Chromebug files from disk before I could even get Firefox to launch.

Firebug actually used to do a better job of debugging our app than it does now – but I don’t know how much the change is down to newer Firefox/Firebug releases, and how much is down to changes in our code. The “debugger” keyword used to work, and the script debugger was very close to working other than getting line counts out of whack resulting in breakpoints occurring at different locations in the code to where they appeared in the script tab. Now none of the script stuff works at all.

The bits that do work mean that Firebug is still a great tool for us, but I do appreciate that it’s first and foremost a tool for HTML development (which is why I haven’t bothered filing bugs about debugging remote-XUL).

By: robcee

robcee — Tue, 20 Oct 2009 12:14:44 +0000

kevin: Rypple encourages short responses so there wasn’t a lot of room there for in depth analysis and suggestion. As Daniel, Mads and Trevan suggest, several people opined that the CSS panel was “useless”. Using it as a validation tool seems to be one of the only uses for it, so maybe reworking it to do that job better would be an improvement.

MarkC: I wish I could help you, but Firebug isn’t really designed to work on XUL apps. Chromebug is probably what you’re looking for, but it could use a little extra love.

You can find a link to it here: http://getfirebug.com/extensions/index.html#chromebug

Thanks for the comments!