Great, it seems console.log works now (it seems other extensions were making it non-effective since FF29).
Firebug 2.0
31–40 of 123 posts
Re: Firebug 2.0
#32Earlier quoted context omitted.
So what if you are the black sheep of the shed?
its like being on yahoo mail when gmail happened or having a new ibm when mac pros happened or doing php when ruby happened, or.. you get the drift.
So everyone like to be on the loop for the sake of being in the loop and not for practical reasons, that is golden!
Re: Firebug 2.0
#33I use Chrome or Firefox built in developer tools, however I still think Firebug fits my workflow the best. Unfortunately it's too slow to use. The thing I miss the most is the inline display of AJAX call responses, and being able to write/run multi-line snippets of JavaScript (without ctrl+enter). Somewhat interestingly, Firefox built their entire add-on architecture because Joe Hewitt wanted dev tools (for debugging…
I hate the fact that the close window/dialog button for the devtools is on the left hand side when every other plugin puts this on the right hand side. I am not an every day user of FF's built in devtools so it is not something that I am accustomed to. Despite firebug's performance troubles when I go to select devtools or firebug I usually opt for firebug simply because the close button drives me nuts.
Re: Firebug 2.0
#34Earlier quoted context omitted.
I find the Firefox dev tools very inferior to Chrome dev tools, missing a lot of "must have" features.
such as? not disagreeing, just wondering what you consider "must have" features that Firefox currently lacks.
Does FF have nice memory tools? I can't see any. I've come to rely a lot of Chromium built in mem tools: Heap snapshot (including diff between snapshots), Record Heap Allocations, Timeline.
Re: Firebug 2.0
#35Still the best developer toolset, on any browser. Unarguably once its combined with FF native tools, and the webdevtoolbar.
I like the search feature in Firebug. Being able to search across all scripts/nodes/stylesheets is rad. Is Chrome Dev Tools' search that good yet? Every time I am working with another dev and want to search for a symbol, I tell the other devs to switch to Firefox/Firebug because Chrome Dev Tools is a mystery of hunting and pecking when it comes to search. (Google is not the best at something-something search??) I cannot understand why other devs are so happy with Chrome.
The Chrome timeline is rad when it comes to performance tuning, and maybe a lot of devs are light on the JS and heavy on the CSS. I jump into Chrome, briefly, whenever I want to tune performance.
All of the dev tools have quirks, bugs, and dumb UI usability issues, but when I want to work with a large codebase (which is every day of my life), I find Firebug works the best.
Re: Firebug 2.0
#36Still the best developer toolset, on any browser. Unarguably once its combined with FF native tools, and the webdevtoolbar.
You can combine Firebug with the FF native developer tools? Like all-in-one in the Firebug UI?
I agree with you on webdevtoolbar, that is a fantastic tool for inspecting/altering aspects of the page. I wish webdevtoolbar had user agent tools. I have to run another plugin to give me user agent spoofing.
Re: Firebug 2.0
#37Earlier quoted context omitted.
such as? not disagreeing, just wondering what you consider "must have" features that Firefox currently lacks.
Does FF have nice memory tools? I can't see any. I've come to rely a lot of Chromium built in mem tools: Heap snapshot (including diff between snapshots), Record Heap Allocations, Timeline.
Yes, extensively; try about:memory for a few of them.
Re: Firebug 2.0
#38Earlier quoted context omitted.
Can you explain why? I've never found a use case that it covers better than Chrome, and it seems to bloat FF a bit. But I'm very willing to believe I just don't understand what it offers.
Chrome still does not support multiline JS console (you need to shift-enter every single lines) See: https://code.google.com/p/chromium/issues/detail?id=35487
This seems more like a different preference than a bug.
Re: Firebug 2.0
#39Earlier quoted context omitted.
I find the Firefox dev tools very inferior to Chrome dev tools, missing a lot of "must have" features.
such as? not disagreeing, just wondering what you consider "must have" features that Firefox currently lacks.
IIRC Firefox builtins don't have a cookie editor.
Re: Firebug 2.0
#40Earlier quoted context omitted.
I find the Firefox dev tools very inferior to Chrome dev tools, missing a lot of "must have" features.
such as? not disagreeing, just wondering what you consider "must have" features that Firefox currently lacks.
I've had trouble with them. They don't include inline stack traces for errors, so you have to do a lot more digging to find what happened and where. Also, in the Network panel, every refresh resets your filters so you have to select XHR every time if you don't want to see a bunch of .html/.js file requests (this may have been fixed in FF v30, haven't tested yet).
There are just a number of really small issues other than those that when you add them up, make the dev toolbar a lot less useful than Chrome. That said, I like Firefox the browser much better than Chrome.