3 ms·

I agree with you that Chrome dev tools are lacking a bit, but what do you miss specifically? I find that the JS debugger is far better (or at least since the l

by scotth 16y ago

I agree with you that Chrome dev tools are lacking a bit, but what do you miss specifically? I find that the JS debugger is far better (or at least since the last time I worked with Firebug). That's enough for me.

hbt 16y ago
- multi-line javascript console - inline viewing of ajax requests - go to link that works - urls that work - keyboard shortcuts for debugging (go to line, create breakpoint) - inspector with more options - easier to edit inline html with highlighting not raw text - connecting to console via other extensions (chrome API is very small compared to firefox API) - Better search in scripts - Better search in DOM tree - Better search in inspector - Less clicking when viewing remote content - Displaying remote content that works (file is loaded, content tab is empty) Only a matter of time before it's implemented in chrome. But, firebug already has all this stuff and it makes a huge difference when debugging JS Note: I wrote a couple of chrome extensions. Therefore, I cumulated more frustration than the average JS developer on chrome because switching to firebug is not even an option in my case ;-)
- scotth 16y ago
  haha, that's a great list. A few of those have bothered me in passing (inline html/css editing, shortcuts, following links without resource tracking). If you need multiline and you're on a Mac (not sure about Windows), you've got option+return in the console.
- catshirt 16y ago
  i did not recognize this until recently so i sympathize; but the chrome inspector has a javascript environment superior to firebug. i do suppose this is arguable, though. more objectively, you can definitely review ajax requests in the inspector- and I actually think this feature is superior as well. interestingly, I actually learned to love the chrome inspector because I was so fed up with using firefox in general (enough so that it's debugging capabilities did not outweigh the cons).
- ELV1S 16y ago
  > - keyboard shortcuts for debugging (go to line, create breakpoint) F1 shows shortcuts. ⌘G: Go to Line How do you create a breakpoint with shortcut?
wanderr 16y ago
In addition to hbt's complaints, the ability to see responses to requests from Flash, and not ripping out get vars from the URL would be incredibly useful (our api all talks to the same endpoint, but the method name is the first get var, making it really easy to find the proper call in Firebug, and a bitch to do the same in Chrome developer tools
8ig8 16y ago
Honestly, now that I think about it, my biggest gripe is that Firebug lite on Chrome feels like an add-on. On Firefox, it feels native, and thus more usable (to me). I've toyed around with various bookmarklet utilities to aid front-end developers. Firebug lite feels like one of those to me. I (maybe wrongly) perceive those as lightweight utilities. Based on your comment, it sounds like my issue may be more with usability than functionality. I haven't even given the lite version enough of a chance since I didn't realize the JS debugger might be superior. For the record, most of the time I'll use Firebug to tweak/debug some CSS. I'll also use it to track down JS issues. I've recently started to use it for server-side debugging with a couple php extensions. Right now, Chrome is my primary browser (OSX). I'd love to use it exclusively, but I still find myself bouncing between the two when developing. (Sometimes I find myself getting lost in a cycle of Safari, Chrome and Firefox windows, but that's a whole 'nother issue.) Edit: Fixed my use of parentheses.
- scotth 16y ago
  I wasn't actually talking about Firebug Lite. I use Chrome Developer Tools (cmd+option+I mac, ctrl+shift+I pc). They are very Firebug-like.

by scotth 16y ago

hbt 16y ago

- multi-line javascript console - inline viewing of ajax requests - go to link that works - urls that work - keyboard shortcuts for debugging (go to line, create breakpoint) - inspector with more options - easier to edit inline html with highlighting not raw text - connecting to console via other extensions (chrome API is very small compared to firefox API) - Better search in scripts - Better search in DOM tree - Better search in inspector - Less clicking when viewing remote content - Displaying remote content that works (file is loaded, content tab is empty) Only a matter of time before it's implemented in chrome. But, firebug already has all this stuff and it makes a huge difference when debugging JS Note: I wrote a couple of chrome extensions. Therefore, I cumulated more frustration than the average JS developer on chrome because switching to firebug is not even an option in my case ;-)

scotth 16y ago
haha, that's a great list. A few of those have bothered me in passing (inline html/css editing, shortcuts, following links without resource tracking). If you need multiline and you're on a Mac (not sure about Windows), you've got option+return in the console.
catshirt 16y ago
i did not recognize this until recently so i sympathize; but the chrome inspector has a javascript environment superior to firebug. i do suppose this is arguable, though. more objectively, you can definitely review ajax requests in the inspector- and I actually think this feature is superior as well. interestingly, I actually learned to love the chrome inspector because I was so fed up with using firefox in general (enough so that it's debugging capabilities did not outweigh the cons).
ELV1S 16y ago
> - keyboard shortcuts for debugging (go to line, create breakpoint) F1 shows shortcuts. ⌘G: Go to Line How do you create a breakpoint with shortcut?

wanderr 16y ago

In addition to hbt's complaints, the ability to see responses to requests from Flash, and not ripping out get vars from the URL would be incredibly useful (our api all talks to the same endpoint, but the method name is the first get var, making it really easy to find the proper call in Firebug, and a bitch to do the same in Chrome developer tools

8ig8 16y ago

Honestly, now that I think about it, my biggest gripe is that Firebug lite on Chrome feels like an add-on. On Firefox, it feels native, and thus more usable (to me). I've toyed around with various bookmarklet utilities to aid front-end developers. Firebug lite feels like one of those to me. I (maybe wrongly) perceive those as lightweight utilities. Based on your comment, it sounds like my issue may be more with usability than functionality. I haven't even given the lite version enough of a chance since I didn't realize the JS debugger might be superior. For the record, most of the time I'll use Firebug to tweak/debug some CSS. I'll also use it to track down JS issues. I've recently started to use it for server-side debugging with a couple php extensions. Right now, Chrome is my primary browser (OSX). I'd love to use it exclusively, but I still find myself bouncing between the two when developing. (Sometimes I find myself getting lost in a cycle of Safari, Chrome and Firefox windows, but that's a whole 'nother issue.) Edit: Fixed my use of parentheses.

scotth 16y ago
I wasn't actually talking about Firebug Lite. I use Chrome Developer Tools (cmd+option+I mac, ctrl+shift+I pc). They are very Firebug-like.