News for hackers. Stuff that matters.
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.