5 ms·

such as? not disagreeing, just wondering what you consider "must have" features that Firefox currently lacks.

gorhill 12y ago
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.
- JoshTriplett 12y ago
  Yes, extensively; try about:memory for a few of them.
  - nnethercote 12y ago
    To be fair, about:memory is designed to be used primarily by Firefox developers. Some web developers will be able to use it effectively, but it is quite intimidating. Happily, memory profiling tools designed for use by web devs are being actively worked on.
    - choudharism 12y ago
      To be honest, it is impressive the kind of detail about:memory manages to provide. But yes, it can be fairly intimidating. That is the problem I tried to address when I tried building a D3 backed front-end over it[1]. [1] https://addons.mozilla.org/en-US/firefox/addon/fx-statistics/ https://addons.mozilla.org/en-US/firefox/addon/fx-statistics...
- mnemonik 12y ago
  I'm working on these tools now, finishing up initial platform work, should start on business logic/UI fairly soon here and get a version 0 out soon. See http://fitzgeraldnick.com/weblog/54/ http://fitzgeraldnick.com/weblog/54/ for some implementation details.
untitaker_ 12y ago
IIRC Firefox builtins don't have a cookie editor.
orthecreedence 12y ago
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.
- danford 12y ago
  > stack traces Starting in Firefox 31, the console will display a full stack trace for errors https://developer.mozilla.org/en-US/docs/Tools/Web_Console https://developer.mozilla.org/en-US/docs/Tools/Web_Console If you're using nightly you already have had a lot of features like this for a while. I find the dev tools in nightly a lot more useful than those in chrome and I prefer the way the dev tools are layed out in nightly. I also like the responsive design view, GCLI, and the eyedropper.
- rafael-rinaldi 12y ago
  Same thing for me. I use Firefox as my main browser and I think it's far better than Chrome, but its native developer tools are just very confusing so I'm sticking with Canary as my development browser.
taf2 12y ago
For me it's the interface - chrome dev tools are similar to what I learned with firebug, where as Firefox builtin tools don't make sense to me. When I need to debug something in Firefox I always install firebug and it's almost the same as if I'm debugging in chrome. Totally a UX thing for me... Happy firebug is still being worked on - it really changed the game in web development.
- kyriakos 12y ago
  i feel the same way. firefox dev tools feel as if they were put together without much thought. a lot of features just thrown all over the place. I still use firebug mostly but chrome dev tools even if not as good as firebug are still a lot better than the firefox ones.
tinco 12y ago
Not that I hate the Firefox devtools, but at the moment I'm using Chrome because there's no way to disable the caching of XMLHTTPRequests in Firefox, and I'm developing a Google Polymer app.
CNojbuHisaVAMCi 12y ago
Mobile tools, especially user agent spoofing per tab and presets for different devices. And disabling of all caches when the developer tools are open. Mobile development with Firefox is a pain compared to Chrome.
vitro 12y ago
One of the features that Chrome has and that is just great is ability to connect resource in the webpage to the resource on your disk. This way, with other tools such as HostAdmin and PerfectPixel you can turn desinged page template into pixel perfect html pretty fast - you just play with the css values in the inspector and your changes write-through to the file on your disk.

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.

JoshTriplett 12y ago
Yes, extensively; try about:memory for a few of them.
- nnethercote 12y ago
  To be fair, about:memory is designed to be used primarily by Firefox developers. Some web developers will be able to use it effectively, but it is quite intimidating. Happily, memory profiling tools designed for use by web devs are being actively worked on.
  - choudharism 12y ago
    To be honest, it is impressive the kind of detail about:memory manages to provide. But yes, it can be fairly intimidating. That is the problem I tried to address when I tried building a D3 backed front-end over it[1]. [1] https://addons.mozilla.org/en-US/firefox/addon/fx-statistics/ https://addons.mozilla.org/en-US/firefox/addon/fx-statistics...
mnemonik 12y ago
I'm working on these tools now, finishing up initial platform work, should start on business logic/UI fairly soon here and get a version 0 out soon. See http://fitzgeraldnick.com/weblog/54/ http://fitzgeraldnick.com/weblog/54/ for some implementation details.

untitaker_ 12y ago

IIRC Firefox builtins don't have a cookie editor.

orthecreedence 12y ago

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.

danford 12y ago
> stack traces Starting in Firefox 31, the console will display a full stack trace for errors https://developer.mozilla.org/en-US/docs/Tools/Web_Console https://developer.mozilla.org/en-US/docs/Tools/Web_Console If you're using nightly you already have had a lot of features like this for a while. I find the dev tools in nightly a lot more useful than those in chrome and I prefer the way the dev tools are layed out in nightly. I also like the responsive design view, GCLI, and the eyedropper.
rafael-rinaldi 12y ago
Same thing for me. I use Firefox as my main browser and I think it's far better than Chrome, but its native developer tools are just very confusing so I'm sticking with Canary as my development browser.

taf2 12y ago

For me it's the interface - chrome dev tools are similar to what I learned with firebug, where as Firefox builtin tools don't make sense to me. When I need to debug something in Firefox I always install firebug and it's almost the same as if I'm debugging in chrome. Totally a UX thing for me... Happy firebug is still being worked on - it really changed the game in web development.

kyriakos 12y ago
i feel the same way. firefox dev tools feel as if they were put together without much thought. a lot of features just thrown all over the place. I still use firebug mostly but chrome dev tools even if not as good as firebug are still a lot better than the firefox ones.

tinco 12y ago

Not that I hate the Firefox devtools, but at the moment I'm using Chrome because there's no way to disable the caching of XMLHTTPRequests in Firefox, and I'm developing a Google Polymer app.

CNojbuHisaVAMCi 12y ago

Mobile tools, especially user agent spoofing per tab and presets for different devices. And disabling of all caches when the developer tools are open. Mobile development with Firefox is a pain compared to Chrome.

vitro 12y ago

One of the features that Chrome has and that is just great is ability to connect resource in the webpage to the resource on your disk. This way, with other tools such as HostAdmin and PerfectPixel you can turn desinged page template into pixel perfect html pretty fast - you just play with the css values in the inspector and your changes write-through to the file on your disk.