The first thing I see is the glaring lack of anti-alias on the Firebug logo.
It looks like a variant of Open Sans, if anyone would point me to it, I can fix it.
Firebug 2.0
41–50 of 123 posts
Re: Firebug 2.0
#42I used to use Firebug extensively. These days, the built-in Firefox developer tools seem to cover everything I need.
Same here. Can any current Firebug users comment as to what they like about it over the built-in tools?
The last thing that still bothers me (now that Firefox 30 added margin/padding highlighting) is that the built in dev tools don't have a way to manage cookies.
Re: Firebug 2.0
#43I really need to stop being so dependent on Firebug. I've done coding sessions or interviews where the other developer only has Google Chrome. Since I use Firebug so much, I am not as proficient with Chrome Dev tools. It makes me look like an amateur when I fumble around. Half the time saying I am used to Firebug is useless since they don't even know what it is.
Most developers I've met have both installed, and wouldn't think twice if you said "I'm better with Firebug, do you mind if we switch browsers?"
Re: Firebug 2.0
#44Re: Firebug 2.0
#45I used to use Firebug extensively. These days, the built-in Firefox developer tools seem to cover everything I need.
Same here, but this feature list looks really nice. I might go back to Firebug.
Re: Firebug 2.0
#46I use Chrome or Firefox built in developer tools, however I still think Firebug fits my workflow the best. Unfortunately it's too slow to use. The thing I miss the most is the inline display of AJAX call responses, and being able to write/run multi-line snippets of JavaScript (without ctrl+enter). Somewhat interestingly, Firefox built their entire add-on architecture because Joe Hewitt wanted dev tools (for debugging…
I hate the fact that the close window/dialog button for the devtools is on the left hand side when every other plugin puts this on the right hand side. I am not an every day user of FF's built in devtools so it is not something that I am accustomed to. Despite firebug's performance troubles when I go to select devtools or firebug I usually opt for firebug simply because the close button drives me nuts.
We moved the button and a number of the tabs in Firefox devtools to be more like the order in Firebug and Chrome devtools. Here's a screenshot from current Nightly: https://i.imgur.com/EmVIZYO.png
Re: Firebug 2.0
#47Earlier quoted context omitted.
I find the Firefox dev tools very inferior to Chrome dev tools, missing a lot of "must have" features.
such as? not disagreeing, just wondering what you consider "must have" features that Firefox currently lacks.
For me it's the interface - chrome dev tools are similar to what I learned with firebug, where as Firefox builtin tools don't make sense to me. When I need to debug something in Firefox I always install firebug and it's almost the same as if I'm debugging in chrome. Totally a UX thing for me... Happy firebug is still being worked on - it really changed the game in web development.
Re: Firebug 2.0
#48I use Chrome or Firefox built in developer tools, however I still think Firebug fits my workflow the best. Unfortunately it's too slow to use. The thing I miss the most is the inline display of AJAX call responses, and being able to write/run multi-line snippets of JavaScript (without ctrl+enter). Somewhat interestingly, Firefox built their entire add-on architecture because Joe Hewitt wanted dev tools (for debugging…
I hate the fact that the close window/dialog button for the devtools is on the left hand side when every other plugin puts this on the right hand side. I am not an every day user of FF's built in devtools so it is not something that I am accustomed to. Despite firebug's performance troubles when I go to select devtools or firebug I usually opt for firebug simply because the close button drives me nuts.
Are you on a mac? I just tried and the close button is on the right.
Re: Firebug 2.0
#49The first thing I see is the glaring lack of anti-alias on the Firebug logo. It looks like a variant of Open Sans, if anyone would point me to it, I can fix it.
Re: Firebug 2.0
#50Earlier quoted context omitted.
such as? not disagreeing, just wondering what you consider "must have" features that Firefox currently lacks.
I've had trouble with them. They don't include inline stack traces for errors, so you have to do a lot more digging to find what happened and where. Also, in the Network panel, every refresh resets your filters so you have to select XHR every time if you don't want to see a bunch of .html/.js file requests (this may have been fixed in FF v30, haven't tested yet). There are just a number of really small issues other t…
> stack traces
Starting in Firefox 31, the console will display a full stack trace for errors
https://developer.mozilla.org/en-US/docs/Tools/Web_Console
If you're using nightly you already have had a lot of features like this for a while.
I find the dev tools in nightly a lot more useful than those in chrome and I prefer the way the dev tools are layed out in nightly. I also like the responsive design view, GCLI, and the eyedropper.