7 ms·

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

by james33 12y ago

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.

simlevesque 12y ago
You can use Aurora right now : http://www.mozilla.org/en-US/firefox/aurora/ http://www.mozilla.org/en-US/firefox/aurora/
givan 12y ago
Firebug is still unbeatable, chrome dev has a lot to catch up.
- diggan 12y ago
  Long time ago I used Firebug. What do you see is better in Firebug than Chrome Devtools?
  - johnward 12y ago
    I 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 12y ago
      Mozilla maintains firebug.
    - fournm 12y ago
      I 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 12y ago
        Ironically 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 12y ago
    my 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 12y ago
      You can enable logging XMLHttpRequests in dev tools settings (gears icon on bottom-right edge) -> console
      - leeoniya 12y ago
        it'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 12y ago
        Just click the request from the console, and it takes you to the network tab where you can see the headers, response, etc.
        leeoniya 12y ago
        to 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
  - rhizome 12y ago
    Chrome 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 12y ago
      I 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)
- dubcanada 12y ago
  I can't stand firebug, the UI is a complete turn off for me. The Chrome dev tools (any any webkit for that matter) just look and function better for what I spend 99% of my time in dev tools doing, tweaking CSS.
  - sergiosgc 12y ago
    It must be a matter of preference, because I can't stand chrome dev tools' ui. Small buttons, cluttered, null use of breathing space in the design.
  - tyilo 12y ago
    I 100% agree with you. I don't care how good the functionality of firebug is.
mundanevoice 12y ago
Same here. I still feel Firefox devtools are not innovating fast enough. Chrome workspaces and a lot of other useful features are just not present in Firefox. I feel that's one of the major reason I could never migrated to Firefox professionally. I am also quite impressed with IE 10 & 11 devtools. It is really useful and has clean UI and UX. In short I could say that: Chrome Devtools > Firebug > IE devtools > Firefox devtools
- mixedbit 12y ago
  I'm a long time Firefox fan, but very recently I played for the first time with IE 11 memory profiler and I must say, this is the best profiler out there.
  - nitrogen 12y ago
    How well does the Linux port perform?
    - pjmlp 12y ago
      The same way as the Safari port.
- cbaleanu 12y ago
  The window title for IE 10&11 devtools is for some reason named "F12" on my windows 7 machine. Maybe it's just me but I find this annoying, feels a little unprofessional.
  - interurban 12y ago
    F12 is the default shortcut for opening the IE devtools, maybe that's why?
    - mbrubeck 12y ago
      Yup, the IE devtools are named "F12" after the keyboard shortcut: http://msdn.microsoft.com/library/ie/bg182326%28v=vs.85%29 http://msdn.microsoft.com/library/ie/bg182326%28v=vs.85%29 (F12 is also the keyboard shortcut for opening the developer tools in Chrome, Firefox, and others.)
angersock 12y ago
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.
- Spittie 12y ago
  As far as I know, the console embedded in the page (ctrl+shift+k) show events only from that page, while the browser console (ctrl+shift+j) show events from all the tabs. I don't know if there is a way to decide which tabs get logged in the browser console.
ossreality 12y ago
Meh, still takes 3-4x as long as Chrome to startup. Fucking unacceptable.
dpcan 12y ago
Arrrg. I use Chrome for everything but I don't like dev tools and consistently use Firefox because it works so much better for me. I've been fearing for a long time now that Mozilla would just start doing whatever Chrome is doing. When it comes to updating dev tools, I wish everything new were an option. When you change a "tool" you change how I "work", and bumps in my work flow just slow me down.

by james33 12y ago

simlevesque 12y ago

You can use Aurora right now : http://www.mozilla.org/en-US/firefox/aurora/ http://www.mozilla.org/en-US/firefox/aurora/

givan 12y ago

Firebug is still unbeatable, chrome dev has a lot to catch up.

diggan 12y ago
Long time ago I used Firebug. What do you see is better in Firebug than Chrome Devtools?
- johnward 12y ago
  I 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 12y ago
    Mozilla maintains firebug.
  - fournm 12y ago
    I 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 12y ago
      Ironically 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 12y ago
  my 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 12y ago
    You can enable logging XMLHttpRequests in dev tools settings (gears icon on bottom-right edge) -> console
    - leeoniya 12y ago
      it'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 12y ago
        Just click the request from the console, and it takes you to the network tab where you can see the headers, response, etc.
        leeoniya 12y ago
        to 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
- rhizome 12y ago
  Chrome 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 12y ago
    I 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)
dubcanada 12y ago
I can't stand firebug, the UI is a complete turn off for me. The Chrome dev tools (any any webkit for that matter) just look and function better for what I spend 99% of my time in dev tools doing, tweaking CSS.
- sergiosgc 12y ago
  It must be a matter of preference, because I can't stand chrome dev tools' ui. Small buttons, cluttered, null use of breathing space in the design.
- tyilo 12y ago
  I 100% agree with you. I don't care how good the functionality of firebug is.

mundanevoice 12y ago

Same here. I still feel Firefox devtools are not innovating fast enough. Chrome workspaces and a lot of other useful features are just not present in Firefox. I feel that's one of the major reason I could never migrated to Firefox professionally. I am also quite impressed with IE 10 & 11 devtools. It is really useful and has clean UI and UX. In short I could say that: Chrome Devtools > Firebug > IE devtools > Firefox devtools

mixedbit 12y ago
I'm a long time Firefox fan, but very recently I played for the first time with IE 11 memory profiler and I must say, this is the best profiler out there.
- nitrogen 12y ago
  How well does the Linux port perform?
  - pjmlp 12y ago
    The same way as the Safari port.
cbaleanu 12y ago
The window title for IE 10&11 devtools is for some reason named "F12" on my windows 7 machine. Maybe it's just me but I find this annoying, feels a little unprofessional.
- interurban 12y ago
  F12 is the default shortcut for opening the IE devtools, maybe that's why?
  - mbrubeck 12y ago
    Yup, the IE devtools are named "F12" after the keyboard shortcut: http://msdn.microsoft.com/library/ie/bg182326%28v=vs.85%29 http://msdn.microsoft.com/library/ie/bg182326%28v=vs.85%29 (F12 is also the keyboard shortcut for opening the developer tools in Chrome, Firefox, and others.)

angersock 12y ago

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.

Spittie 12y ago
As far as I know, the console embedded in the page (ctrl+shift+k) show events only from that page, while the browser console (ctrl+shift+j) show events from all the tabs. I don't know if there is a way to decide which tabs get logged in the browser console.

ossreality 12y ago

Meh, still takes 3-4x as long as Chrome to startup. Fucking unacceptable.

dpcan 12y ago

Arrrg. I use Chrome for everything but I don't like dev tools and consistently use Firefox because it works so much better for me. I've been fearing for a long time now that Mozilla would just start doing whatever Chrome is doing. When it comes to updating dev tools, I wish everything new were an option. When you change a "tool" you change how I "work", and bumps in my work flow just slow me down.