11–20 of 118 posts
Wow, I'm really impressed with the strides Mozilla has been making on this front. Chrome has long had the best dev tools and is one of the reasons I hardly ever use Firefox anymore. Once these updates land it may be on par or even better. Excited to see true competition on the dev side of things now.
Firebug is still unbeatable, chrome dev has a lot to catch up.
Wow, I'm really impressed with the strides Mozilla has been making on this front. Chrome has long had the best dev tools and is one of the reasons I hardly ever use Firefox anymore. Once these updates land it may be on par or even better. Excited to see true competition on the dev side of things now.
This is probably a really dumb question, but is there any way to get Firefox to limit console output to just the current window? I've had a tab open (Grooveshark, in this case) leak messages over into what I'm actually trying to debug, and it's pretty annoying.
I don't know if there is a way to decide which tabs get logged in the browser console.
I think it's almost funny, but a cURL command line could become the common interface for many tools.
Oh look, a bunch of updates to catch up to Chrome's tools again .
Does Chrome have in-REPL stack traces? An eyedropper tool? Multiple cursor support?
Sure, the cURL copy thing and style support in the console were first implemented in WebKit (not Chrome or Blink), but I think most of these features are leapfrogging Chrome's capabilities, not only attaining parity.
The add-on debugger is the big part of this update. Add-on dev is a pain in the ass on Firefox, and I hope this helps.
Compare it with Chrome where you can see the error, it show where the problem is and you can even edit/patch the addon live without having to restart the browser.
Earlier quoted context omitted.
Firebug is still unbeatable, chrome dev has a lot to catch up.
Long time ago I used Firebug. What do you see is better in Firebug than Chrome Devtools?
I also wonder why Mozilla didn't attempt to acquire firebug instead of building their own tools from scratch?
Earlier quoted context omitted.
Firebug is still unbeatable, chrome dev has a lot to catch up.
Long time ago I used Firebug. What do you see is better in Firebug than Chrome Devtools?
- 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.