Re:Firebug 2.0
by ben336 on Tuesday June 10, 2014 @01:18PM
(#7873895)
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.
[ Parent
| on HN ]
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 paste that into your terminal and you can keep retrying indefinitely without having to click/interact with the web page at all. Hugely useful if you're debugging the server side of a client->server interaction.
Re:Firebug 2.0
by jrochkind1 on Tuesday June 10, 2014 @04:42PM
(#7875203)
Chrome dev tools has that too these days. Copy as curl.
these days == for years
Re:Firebug 2.0
by TazeTSchnitzel on Wednesday June 11, 2014 @07:45AM
(#7877453)
Chrome and Firefox both have that.
Chrome dev tools lacks in the DOM view of firebug. Firebug makes it easy to search and identify all the DOM objects.
Chrome still does not support multiline JS console (you need to shift-enter every single lines)
See: https://code.google.com/p/chromium/issues/detail?id=35487
That is useful, but doesn't really seem to cover the original comment's assertion that Firebug is still "inarguably the best"
Re:Firebug 2.0
by SquareWheel on Tuesday June 10, 2014 @02:31PM
(#7874430)
This seems more like a different preference than a bug.