Earlier quoted context omitted.
Can you explain why? I've never found a use case that it covers better than Chrome, and it seems to bloat FF a bit. But I'm very willing to believe I just don't understand what it offers.
One thing that I found indicative of the "depth" of Firebug is the very simple context menu item when you right-click a URL in the Network tab: "Copy as Curl command" (the text may read differently, this is from memory). It creates a clipboard entry which contains a "curl" command line with all the cookie/header/etc. data that would be sent from your browser if you were to request that URL (via Ajax or whatever). You…
Firebug 2.0
111–120 of 123 posts
Re: Firebug 2.0
#112Earlier quoted context omitted.
I'm always surprised when I read comments about how the Firefox devtools offer the best developer experience. Every single one of these new features (except searching the dom via CSS selectors or regex) have been available in Safari's Web Inspector for OS X for at least a year. Plus, I think the UI is more thought out and easy to use in Safari. Can someone explain what Safari's Web Inspector is lacking?
It doesn't run on PCs.
Re: Firebug 2.0
#113Earlier quoted context omitted.
I find the Firefox dev tools very inferior to Chrome dev tools, missing a lot of "must have" features.
If you are using Firefox for testing front-end, I suggest using Nightly as a copy for dev tool. You will get the latest goodies.
Re: Firebug 2.0
#114I 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…
Re: Firebug 2.0
#115about:config -> devtools.inspector.enabled -> false
Re: Firebug 2.0
#116I used to use Firebug extensively. These days, the built-in Firefox developer tools seem to cover everything I need.
I find the Firefox dev tools very inferior to Chrome dev tools, missing a lot of "must have" features.
Re: Firebug 2.0
#117I 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.
If they don't know what Firebug is, they're not versed in the tools of the trade. You should consider that to be a very serious red flag about working with them. (Edited for tone)
Re: Firebug 2.0
#118Earlier quoted context omitted.
If you are using Firefox for testing front-end, I suggest using Nightly as a copy for dev tool. You will get the latest goodies.
Easy way to install them both?
Re: Firebug 2.0
#119Earlier quoted context omitted.
Can you explain why? I've never found a use case that it covers better than Chrome, and it seems to bloat FF a bit. But I'm very willing to believe I just don't understand what it offers.
One thing that I found indicative of the "depth" of Firebug is the very simple context menu item when you right-click a URL in the Network tab: "Copy as Curl command" (the text may read differently, this is from memory). It creates a clipboard entry which contains a "curl" command line with all the cookie/header/etc. data that would be sent from your browser if you were to request that URL (via Ajax or whatever). You…
Re: Firebug 2.0
#120Earlier quoted context omitted.
If you are using Firefox for testing front-end, I suggest using Nightly as a copy for dev tool. You will get the latest goodies.
Easy way to install them both?
https://support.mozilla.org/en-US/kb/profile-manager-create-...
This way you can open as many firefox as you want.