4 ms·

Any particular feature you would like, that is missing?

by sawrubh 12y ago

pjmlp 12y ago
- The whole resources view - JavaScript profiling (heap, cpu, events) - DOM events monitoring and breakpoints. - JavaScript code completion
- danford 12y ago
  > - 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 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.
  - mateuszf 12y ago
    Another thing: stack traces allowing to go back even after async calls / promises.
  - pjmlp 12y ago
    > > - 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/resource-panel 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.
    - deleted 12y ago
      [deleted]
    - danford 12y ago
      >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_Monitor 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.
      - pjmlp 12y ago
        > 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.
        bgrins 12y ago
        > 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 https://bugzilla.mozilla.org/show_bug.cgi?id=970517
- rlx0x 12y ago
  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.
  - pjmlp 12y ago
    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.
- mnemonik 12y ago
  > The whole resources view https://bugzilla.mozilla.org/show_bug.cgi?id=926449 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=8410336 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/ http://fitzgeraldnick.com/weblog/54/ And here is a design mockup (won't be exactly like this): https://people.mozilla.org/~dhenein/devtools/memtools/#/memory 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 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 https://bugzilla.mozilla.org/show_bug.cgi?id=968896
  - pjmlp 12y ago
    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/timeline 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.
buttsex 12y ago
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.

Any particular feature you would like, that is missing?

by sawrubh 12y ago

Any particular feature you would like, that is missing?

pjmlp 12y ago

- The whole resources view - JavaScript profiling (heap, cpu, events) - DOM events monitoring and breakpoints. - JavaScript code completion

danford 12y ago
> - 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 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.
- mateuszf 12y ago
  Another thing: stack traces allowing to go back even after async calls / promises.
- pjmlp 12y ago
  > > - 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/resource-panel 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.
  - deleted 12y ago
    [deleted]
  - danford 12y ago
    >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_Monitor 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.
    - pjmlp 12y ago
      > 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.
      - bgrins 12y ago
        > 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 https://bugzilla.mozilla.org/show_bug.cgi?id=970517
rlx0x 12y ago
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.
- pjmlp 12y ago
  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.
mnemonik 12y ago
> The whole resources view https://bugzilla.mozilla.org/show_bug.cgi?id=926449 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=8410336 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/ http://fitzgeraldnick.com/weblog/54/ And here is a design mockup (won't be exactly like this): https://people.mozilla.org/~dhenein/devtools/memtools/#/memory 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 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 https://bugzilla.mozilla.org/show_bug.cgi?id=968896
- pjmlp 12y ago
  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/timeline 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.

buttsex 12y ago

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.