- why can't I drag and drop DOM elements in the inspector?

- Chrome's autocomplete seems smarter. If I go to edit a style and I type `li` Chrome gives me line-height, FF gives me lighting-color?

- I prefer the color highlight when you hover over DOM elements in the inspector, I can see the box model in Chrome but just a dotted outline in FF.

FF's tools do seem to get better and more robust with each update though.

- JavaScript profiling (heap, cpu, events)

- DOM events monitoring and breakpoints.

- JavaScript code completion

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

Here's a screencap of the WIP (ignore the text): https://bug970517.bugzilla.mozilla.org/attachment.cgi?id=841...

> JavaScript profiling (heap, cpu, events)

We have CPU profiling now, but we are in the process of reworking the UI to make it more useful and include a better presentation for events and how they fit into that picture.

I'm working on memory tooling. Here is some more info: http://fitzgeraldnick.com/weblog/54/

And here is a design mockup (won't be exactly like this): https://people.mozilla.org/~dhenein/devtools/memtools/#/memo...

> DOM events monitoring and breakpoints.

We have break on dom events already: http://i.imgur.com/RDy7BXy.jpg

What do mean by monitoring? Would be interested in hearing more about what you're talking about and the use cases.

> JavaScript code completion

We have had this in the console for a long time, and it is coming in the scratchpad very soon: https://bugzilla.mozilla.org/show_bug.cgi?id=968896

> What do mean by monitoring? Would be interested in hearing more about what you're talking about and the use cases.

Maybe I expressed myself incorrectly. I mean this type of information profiling.

https://developers.google.com/chrome-developer-tools/docs/ti...

Very useful to track down where some, sometimes pesky, JavaScript code has bound events to the DOM.

This is a big debugging pain, to track down why events are being triggered, or not working, in a certain way and what JavaScript code is responsible for it.

I'm not sure what the exact criticism is here.

> - JavaScript profiling (heap, cpu, events)

is this what you mean?

https://developer.mozilla.org/en-US/docs/Tools/Profiler

> - DOM events monitoring and breakpoints.

You can do this now (at least in nightly)

> - JavaScript code completion

Works in the JS console.

> I'm not sure what the exact criticism is here.

How can I see the whole data available to the browser in FF, similar to ChromeDev Tools

https://developers.google.com/chrome-developer-tools/docs/re...

> - DOM events monitoring and breakpoints.

> You can do this now (at least in nightly)

Cannot install nightly versions on customers. Good to know it is coming, though.

> > - JavaScript code completion

> Works in the JS console.

But not yet on the Scratchpad, unless I am missing something.

It's a lot different than what chrome does, but I believe they're integrating the resources with the network tab: (scroll to the bottom where the pie charts are.)

https://developer.mozilla.org/en-US/docs/Tools/Network_Monit...

> Cannot install nightly versions on customers

Do your customers develop web pages? If so why are they paying you to install a browser?

>But not yet on the Scratchpad

This appears to be true.

Thanks for the link. What about IndexDB, Web SQL and Local Storage?

> Do your customers develop web pages? If so why are they paying you to install a browser?

They surely do. My employer does Fortune 500 consulting and many times we get to use what their IT allows us to.

Not yet, but a storage inspector panel is being worked on: https://bugzilla.mozilla.org/show_bug.cgi?id=970517

It always amuses me when people think the Firefox Developer Tools are equal to the Chrome DevTools. They really can't be using either of them very much.

ChromeDev tools remind me of working in Smalltalk. Still not quite there yet, but real close.

Although I also find quite good that FF tooling is improving, as web development requires testing across all major browsers anyway.

Besides, Mozilla is not trying to tie down anyone to it's platform, because the platform is basically the Web, which is open to everyone. There are many things which distinguish it from other platforms like you can host your "apps", which are nothing more than simple websites, on your own site and not necessarily Mozilla's MarketPlace. Mozilla is working hard to reduce the memory footprint and make the apps responsive[1] and by the time it comes out, I think it's going to have a really good performance.

[1] - https://bugzilla.mozilla.org/show_bug.cgi?id=797189

Btw I tried this in the latest Firefox nightly and it seems that the nightly doesn't crash although the CPU usage does go up to 50%, so it seems that this bug has been fixed and will be released in the upcoming stable releases.