Live data from Hacker News

Firebug 1.12 – New Features

hacks.mozilla.org

1–10 of 37 posts

Re: Firebug 1.12 – New Features

#5

Love the new features. I still find myself using Firebug over the built in dev tools in either Chrome or Firefox. The Firebug team has done a really tremendous job over the years. Keep up the good work!

Yeah, firebug still has quite a lot of polish compared to the others.

Perhaps it has to do with the contributors being expert UI developers, and firebug developers second. Whereas the other tools are mostly developed by employees who do full time dev tool development, but not so much work using the tools.

But I know others mostly prefer chrome tools. The same people often get stuck in firebug or in IE dev tools.

Anyway... GREAT WORK FIREBUG TEAM! xo

Re: Firebug 1.12 – New Features

#6

Is there work going on to build Firebug on top of the built-in Firefox debugging tools? The two don't seem to work well together at the moment.

Not really, no. There was some talk about adding a Firebug panel to the built-in tools, but nothing has really come from it, and any deeper UI integration is probably out of the question for being too much work. But suggestions about how to make it better are still welcome, of course.

The main thing we have gotten out of the new devtools are new cool APIs, e.g. for debugging, paint flashing, CSS auto-completion, profiling (though we haven't gotten around to using most of them yet).

Re: Firebug 1.12 – New Features

#8
post #5

Love the new features. I still find myself using Firebug over the built in dev tools in either Chrome or Firefox. The Firebug team has done a really tremendous job over the years. Keep up the good work!

Yeah, firebug still has quite a lot of polish compared to the others. Perhaps it has to do with the contributors being expert UI developers, and firebug developers second. Whereas the other tools are mostly developed by employees who do full time dev tool development, but not so much work using the tools. But I know others mostly prefer chrome tools. The same people often get stuck in firebug or in IE dev tools. Anyw…

I fail to see how Firebug has a better UI then WebKit Developer Tools?

As far as I am concerned they are the same in that regard. And since both of those tools are not built by "developers", but by "frontend engineers" it doesn't really matter.

I spent like 15 minutes trying to figure out how to attach Firebug to the browser window. Only to find out that the upward pointing arrow in a gray circle means attach to browser window. On WebKit I click an icon that looks like a browser window with developer tools.

The resources tab in WebKit is ten times better then the mishmash of CSS/Script/Net/Cookies tabs all spread out.

Anyways that is just my opinion, and as far as I am concerned Dragonfly was the best.

Re: Firebug 1.12 – New Features

#9
post #7

"Copy as cURL" is great! I'm curious to see if it even builds POST requests properly.. Edit: it does! It includes all the headers, the POST data, etc...

Even the cookies. It's been in webkit for a while. SO USEFUL.

You can also use it to leech stuff from login/captcha protected download areas like rapidshare or the apple dev center. No more failed browser downloads of 1gig files! Just add -C to your curl command!

Re: Firebug 1.12 – New Features

#10
post #7

"Copy as cURL" is great! I'm curious to see if it even builds POST requests properly.. Edit: it does! It includes all the headers, the POST data, etc...

Well Chrome had this feature for a long time. Personally I don't find it much useful. But to me the killer feature of firebug is that when you open an XHR entry in new tab it opens the tab with all POST variables. Super handy when debugging REST api.
Post reply on HN