What features does Firebug have that Chrome's Developer Tools do not have? [closed]

Answer 1

I feel a lot more comfortable using Firebug. I can't think of specifics at the moment, but sometimes I'll try debugging something in Safari or Chrome and it seems like such a PITA that I launch Firefox and get whatever done quickly.

The DOM tab is a plus, for one. It's more accessible and well laid out than Chrome's equivalent. I prefer the way DOM and other JS objects are logged to the console in Firebug, too.

Firebug plug-ins like Pixel Perfect are very useful as well. I don't know whether any such tool exists for Chrome.

Overall, it doesn't matter because you have to test in both browsers, anyway. And IE, so might as well compare it to IE's Dev tools (which have improved, but still are not good compared to FF or Webkit's).

I don't think there's anything advanced in particular present in Firebug but not in Chrome that you'll be missing.

Answer 2

Almost made the switch today but I noticed I can't right click on modified CSS in Chrome and copy the Rule or Style declarations like I can in firebug. GOD I wish firefox didn't suddenly start sucking or I wouldn't have this problem.

Answer 3

"Edit and Resend" request feature

With "Edit and Resend" feature in Firefox Developer tools (Replay XHR or something in Firebug), you can replay the XHR request with changes in the request including request headers, request body, http method and even url. Google Chrome's Replay XHR simply replays the request, and does not allow any modifications to the request.

I use Firefox Devtools when I need this feature.

Answer 4

Adding my few cents...

1. Chrome Inspector could not sort the CSS properties alphabetically where as Firebug could do this like a charm. It helps when you inspect some css element and need to grab it firebug comes handy on this.

   As per good CSS coding practice, its always better to have your CSS properties sorted alphabetically in your code.

2. When you are working on a project involved with lot of scripts.In firebug under script tag you have an option of searching for a js file in the suggestion box provided. Where as with chrome you will have a lame tree view to locate your JS file which is tedious to see the namespacing of your js file and traverse the tree.

   This option might not affect anyone who involves with little JS files in their project. This feature is a bang on with firebug I use when my scripts are more than 1000 JS files.

Answer 5

I love Chrome dev tool but sometime I missed these powerful feature from firebug.

• Conditional breakpoint : pause only on specific condition.
• Logging function calls : mark the function and see everything you want to know in console.
• Break On Property Change : Mark objects and debugger will pause if property get changed.

Answer 6

I haven't run into a Firebug feature I've missed yet after switching to Chrome.