5 ms·
Long time ago I used Firebug. What do you see is better in Firebug than Chrome Devtools?
by diggan 13y ago
Long time ago I used Firebug. What do you see is better in Firebug than Chrome Devtools?
- johnward 13y agoI think the chrome devs did a good job of incorporating the best firebug features. The things that I find better in Firebug are mostly add-ons. For example I work with xpath a lot so firepath work awesome and ties into firebug seamlessly. I haven't found a tool that works as well on chrome. I also wonder why Mozilla didn't attempt to acquire firebug instead of building their own tools from scratch?
- mixedbit 13y agoMozilla maintains firebug.
- fournm 13y agoI believe Mozilla does manage Firebug, but the reason it isn't integrated as the main set of tools has to do with Firebug being much slower on complex pages?
- conradfr 13y agoIronically I don't get console log in Firebug anymore since FF 29 (conflicts with other plugins it seems ?), so that forces me to use the dev tools.
- leeoniya 13y agomy peeves (in order of annoyance, desc): - inspecting ajax responses in console without flipping to net panel, then hunting for the correct request. - keeping an inspected/selected html element highlighted on page, not just on mouseover so you can see element bounds. this is useful for tweaking sizing, padding, margins and position. - as-i-type updating of html rather than on blur - live highlighting html as it changes - multiline console - can't arrange the console tab to be first or arrange the tabs in my most frequently used order. to be fair, FB doesnt offer this either, but I like the console to be first since i spend 90% of my time there in FB, probably cause it's much more useful than chrome's. there's more that dont immediately come to mind, but not having the first 2 is a major nuisance and productivity killer.
- smalu 13y agoYou can enable logging XMLHttpRequests in dev tools settings (gears icon on bottom-right edge) -> console
- leeoniya 13y agoit's not at all useful. all you get is some stack-tace-like thing without any of what you actually want to see. like req/resp headers and body, params, inline json/html decoding based on response type. chrome lags here by a large margin.
- clarkm 13y agoJust click the request from the console, and it takes you to the network tab where you can see the headers, response, etc.
- leeoniya 13y agoto see the response body of a request in chrome: 1. Click request in console 2. Find and click request again in Net panel 3. Click Preview or Response tab 4. Click console again to return and then... 5. Oh wait, want to see something in the headers 6. Rinse and repeat. In FB: 1. Click request in console. 2. See raw response body right away, or click headers to see headers or json/html to see those rendered nicely. 3. bonus: view multiple json requests in same window
- magicalist 13y agoIt's actually more like 1. Click request in console 2. Click on the request that was just highlighted for you in the Net panel 3. See headers right away, or click Response to see raw response or Preview to see those rendered nicely 4. Click console again to return and then... 5. Oh wait, want to see something in the headers 6. Go to the Net panel, still there for you It's a different workflow and it's probably annoying to you since you're not used to it, but "it's not at all useful" is edging past hyperbolic. Personally I feel like a clumsy idiot when I go back to Firebug, even though I used to live in it and once knew every quirk. I think that's just the way of developer tools.
- rhizome 13y agoChrome adamantly refuses to un-enable responsive useragent stuff. I constantly have to turn off the extra half-window. More evidence that Google has little product sense.
- grrowl 13y agoI agree, while Chrome DevTools are superior in many ways, it's become a shambles as they shoehorn features wherever they fit (like that console half-window)