Biggest thing I'm missing in the FF Aurora builds is a console in the Inspector / Debugger panes. Having to switch to the console pane all the time gets annoying quickly.
Is there any plan to expose some of these new features (subpanes, docking mode) to the developer command line tools as well? Being able to do something like this would be very nice:
inspect body --font
console open --side
(That aside, developer command line tool[1] is already a big productivity booster. You should check it out if you haven't.)
I must admit that I find Chrome's devtools the easiest to use, but that's probably because it's what I'm most used to.
I work at a web dev company and there's a pretty obvious split between people who prefer FF or Chrome devtools. Every time someone says "but you can do this with x devtools but not in y devtools", it's met with a member of the other party saying something to the effect of "yes you can! it's here!". I think it's just a matter of opinion/what you're used to.
You can't get a formatted treeview of raw JSON post data in chrome inspector, only the response can be inspected in this way. Makes debugging broken uploads difficult at times. That's pretty much the only feature of firebug I miss.
The only chrome inspector feature I know of that firebug doesn't have a real equivalent for is the heap snapshot and compare tool. Really handy to track down memory leaks.
Other than that it's indeed down to personal preference.
The re-painted feature is a very nice idea. It will really be useful when you it's available in a number of browsers, so that you can compare the results.
I'd rather have a cross browser developer console. It would be easier to have the information in the same in format when debugging browser issues.
One thing I've found frustrating with Webkits console is the introduction of shortcuts recently (year ago?). In particular I'm used to hitting cmd-L to get to the onmibar but if I'm in the tools it does something else now (modal controla = bad).
Then I have to use the mouse, which makes me sad :(
* method and name column swapped
* green/yellow status icons added (probably 200/304?)
* dark color scheme vs light color scheme
Is there something I'm missing? Because it sure doesn't seem like the MS Word super-toolbar you compared it to.
Or is it the tab icons? Chrome recently disabled those by default, and I'd agree that they do seem like clutter.
Edit: Misread the comment you were replying to. I thought you were comparing the number of icons and tabs, but you're just talking about the size of the elements. Firefox is slightly larger, yeah.
1. Nice contrast, good padding
2. Why not the same padding as 1.?
3. To much vertical padding. Contrast: are those deactivated?
4. To much vertical padding.
5. Why is this font so huge?
But I have to admit, the situation got better not worse in the last versions.
But Chrome imho also has the smarter solution in the network panel: workflow over more panes. You click a request and you see the details in the main area replacing the waterfall, not adding another pane fighting for space.
Breakpoints are limited - In chrome, I can watch for events and have it break on them. If I'm wanting to debug minified code, in chrome I make it readable and set breakpoints.
Would be nice to edit the JavaScript as well in the process of debugging it. JS Breakpoints currently (in nightly) block loading of the JavaScript file the breakpoint is in. The file is loaded, just not visible in the debugger.
From the tools, no way to see data like cookies or local storage (Cookies can be seen on the network tab, but it's not the same). Chrome has this in a Resources tab.
Chrome's timeline.
The style editing options in the inspector are limited. Sure, the style editor is a colorized text editor, but there is no easy way to edit styles as in Chrome. Chrome, I can set states and work with them without worry. Editing CSS is also easier with auto-complete. Basically, editing in CSS in Chrome is better than in Firefox.
There are a lot of little things. They are catching up. I can get some of these things in Firebug, but then I'd be using Firebug.
Finally, the console is limited. In Chrome, I can bring up the console on any section. This is important, as it lets me use the console while looking at the information I'm currently working with for reference.
There are things I like, and I'm looking forward to the day it's comparable and meets my needs.
"Would be nice to edit the JavaScript as well in the process of debugging it. JS Breakpoints currently (in nightly) block loading of the JavaScript file the breakpoint is in. The file is loaded, just not visible in the debugger."
This is huge for me, it makes debugging impossible when loading.
Each of the aspects you tackle are known and we are working towards improvements in each area. Even myself as a web developer I find things that we are missing - I understand your pains here!
Break on events and break on XHR is something we really want to have ASAP. I expect these will be among the first ones to land - from the things you mention.
Also, make sure you try the new net monitor in Firefox Nightlies.
For me the biggest problem is that it doesn't clear upon reload. Having to keep track of which messages/errors came from the previous page is really annoying.
Edit: Also, viewing objects is inferior compared to Chrome's tools.
You might want the ability to clear console on page reload as an option. It seems useful and people should be able to enable/disable it (or was it added to new nightly).
I can because I just found that very useful. Think of code that has an error in an window.onbeforeunload handler. By the time the console displays the error the page has switched. Without being able to view the errors from the previous page, this would have been impossible to catch.
At first it felt significantly worse for me, but as I started using it there is no significant difference. Webkit's is prettier and I like the being able to refresh to clear it though.
That font inspector looks awesome. I've wanted exactly this several times before.
It's often surprisingly difficult to pin down exactly what font the browser chooses. You can look at the CSS font declaration (which is often hard enough to find in complex CSS), but what if the browser didn't go with the first option?
Looks like they're finally making my add-on - https://addons.mozilla.org/en-us/firefox/addon/font-finder/ - obsolete. Frankly, all I can say is about time. This is something that I would've expected to be able to do long ago, and I welcome my new font analysis overlord.
I've been giving the nightly builds a real shot at replacing the main browser I do my development in, but I've been sorely missing a shortcut to clear the console output, ie ⌘K in the webkit inspector. As far as I know, the only way to clear the console is either clicking "clear" or invoking clear(); in the console itself.
It used to be that I could close the inspector in FF by hitting escape. I would love to get that functionality back it makes it super easy to go in and out of it. (Ctrl+Shift+I) do thing (ESC)
If I recall correctly, Firebug had to do nastier and nastier black magic in order to hook into the correct parts of the rendering engine and provide the data it had. This meant both that Firebug was a poor experience to develop for, and also that it constrained Mozilla to not break certain internal interfaces, even though they weren't designed for public consumption.
A tool like this really does need to go into the browser as a first-class thing, because the information it needs access to is very low-level. So, the Firefox team is making their own. As a side benefit, it should be much easier to write, since they have the power to actually change Firefox to make the information they want easily available.
