News for hackers. Stuff that matters.
Re:Firefox 29 by pjmlp on Tuesday April 29, 2014 @09:31AM (#7666805)
Already using it.

I am impressed with the updated supported on the developer tools, although Chrome DevTools still wins in tooling.

Re:Firefox 29 by sawrubh on Tuesday April 29, 2014 @09:45AM (#7666903)
Any particular feature you would like, that is missing?
Re:Firefox 29 by buttsex on Tuesday April 29, 2014 @03:10PM (#7669289)
I like the update, looks a lot better. It is the small details that keep me using Chrome's dev tools. For instance,

- 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.

Re:Firefox 29 by pjmlp on Tuesday April 29, 2014 @10:07AM (#7667038)
- The whole resources view

- JavaScript profiling (heap, cpu, events)

- DOM events monitoring and breakpoints.

- JavaScript code completion

Re:Firefox 29 by mnemonik on Tuesday April 29, 2014 @02:36PM (#7669065)
> The whole resources view

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

Re:Firefox 29 by pjmlp on Tuesday April 29, 2014 @03:02PM (#7669237)
Thanks for jumping in. Lots of interesting information.

> 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.

Re:Firefox 29 by danford on Tuesday April 29, 2014 @10:23AM (#7667141)
> - The whole resources view

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.

Re:Firefox 29 by pjmlp on Tuesday April 29, 2014 @10:56AM (#7667371)
> > - The whole resources view

> 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.

Re:Firefox 29 by danford on Tuesday April 29, 2014 @11:19AM (#7667568)
>How can I see the whole data available to the browser in FF, similar to ChromeDev Tools

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.

Re:Firefox 29 by pjmlp on Tuesday April 29, 2014 @11:32AM (#7667652)
> 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.)

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.

Re:Firefox 29 by bgrins on Tuesday April 29, 2014 @02:46PM (#7669137)
> Thanks for the link. What about IndexDB, Web SQL and Local Storage?

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

Re:Firefox 29 by mateuszf on Tuesday April 29, 2014 @10:46AM (#7667294)
Another thing: stack traces allowing to go back even after async calls / promises.
Re:Firefox 29 by rlx0x on Tuesday April 29, 2014 @10:49AM (#7667308)
besides the ever-growing list of powerful features (async stack traces?!), I would add usability, I regret clicking "Inspect element (Q)" every time, also the only reason I have a chromium running I prefer firefox otherwise ;)

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.

Re:Firefox 29 by pjmlp on Tuesday April 29, 2014 @10:59AM (#7667398)
Even though as my HN history will show, I prefer native over web, I do work a lot in web projects.

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.

Re:Firefox 29 by danford on Tuesday April 29, 2014 @10:05AM (#7667024)
I've been on nightly for as long as I can remember and at this point I'd say I can't find any feature that Chrome has that I really need (as a web dev). I guess once you get used to one toolbox it's hard to switch. I'm also amazed at the speed at which firefox has caught up to chrome in this area. Chrome dev tools have some features that aren't in firefox yet, but firefox has some tools that aren't in chrome.

Where are the FF dev tools lacking for you?

Re:Firefox 29 by pjmlp on Tuesday April 29, 2014 @10:08AM (#7667043)
Re:Firefox 29 by koide on Tuesday April 29, 2014 @09:48AM (#7666923)
firebug fits the bill nicely. not sure why it's not merged.
Re:Firefox 29 by fournm on Tuesday April 29, 2014 @10:12AM (#7667065)
The built in dev tools are really quickly catching up to and passing Firebug in some areas--I'm not sure how far they are in 29, but in the Aurora/Nightly channels they've just about made me uninstall Firebug (so far, old habits are still dying hard, though).

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