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.)
- 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 ;-)
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).
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
For anyone using the "color picker" extension, there is a better option (Windows only, sorry). I use ClipX, which is a utility for having clipboard history (i.e., you can ctrl+c 10 things and have them all available.) It's amazingly useful, and works exactly as you'd expect out of the box.
It has an extension called Color Picker, which gives you a shortcut for popping up a Color Picker/Eye Dropper tool whenever and wherever you want, anywhere inside you Operating System. It's customizable as to what exactly gets copied to your clipboard. It is a much better option than having an extension, IMO, both because it's part of a utility I use anyway, and because it is available anywhere inside Windows, not just your browser.
For OSX I use 'DigitalColor Meter', comes with all OS X's and isn't browser based. Can do Hex + RGB, install Afloat and you can keep it above all windows on your mac.
As much as I liked that list, I stopped from installing all of them, because they scare me. Call me stupid and paranoid, but I dont understand why a friggin "color-picker"-extension would require full access to my browsing history. If anyboy can explain, I d be glad to be informed on why that is.
The color picker module does not do what is stated in this article, did they even try it? The feedback section for color picker is riddled with comments that it doesn't do what people would naturally think it would do (pick out a color on the page using an 'eye dropper' like functionality.
Fortunately, there is both an actual 'eye dropper' extension and the 'color pick' extension. Eye dropper never worked for me on my Linux box, but color pick works like a charm. Here is its extension page: https://chrome.google.com/extensions/detail/ohcpnigalekghcmg...
- Evernote Web Clipper - for saving code snippets and notes about projects
- Resize Window - to open a page in a resolution of your choice. Very useful.
- Awesome Screenshot - take a screenshot and let people know what you think about a page ... if you're using Safari, Coda Notes is much nicer, though :)
And, of course, the developer tools included in Chrome (first in Safari ... and they still are nicer there) are great, too.
It needs a bit more work (if you compare it to vimperator on firefox).
Especially some essential things like cursor mode, visual mode, bookmarks and keymarks
I don't know how the article missed Speed Tracer. https://chrome.google.com/extensions/detail/ognampngfcbddbfe...