3 ms·
- multi-line javascript console - inline viewing of ajax requests - go to link that works - urls that work - keyboard shortcuts for debugging (go to line, c
by 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 agohaha, 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 agoi 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?