[shiloa]

I love firefox and use it daily for my work. The only time I switch to Chrome is when I use console.log(<some object or DOM node>) and get an [Object object] printed out. Sure I can click on it and get a breakdown (still haven't figured out how to close that view other than closing and re-opening the dev tools pane, BTW), but Chrome handles it much better by logging out a detailed, interactive object.

Still, great job to the FF team and keep up the good work!

[RussianCow]

Firebug does it in a way similar to Chrome, as well. This is really my last withstanding gripe with the Firefox developer tools; if they make logging objects more useful, I will drop Firebug in a heartbeat.

[canuckistani]

You can use console.dir to get an inline browse-able object, does that help?

See this screenshot:

http://note.io/HxSxmK

[RussianCow]

It helps, but the key feature of Firebug for me in this regard is that, if the object is an HTML element, I can click on it and it will take me to that element in the HTML view. The built-in tools don't have this yet.

[canuckistani]

There is the bug for nearly that exact thing:

https://bugzilla.mozilla.org/show_bug.cgi?id=890402

I linked to this comment in that bug, thanks for the feedback!

[robcee]

ESC key to close that sidebar in the console.

[shiloa]

Works - thanks for the tip. A simple [x] icon (perhaps with a "click ESC to close" tooltip) will also be nice, as there's currently no visual indication on how to close it.