4 ms·

From the top of my mind: 1. HTTP Request builder (think cURL with a nicer GUI and the ability to save presets); 2. Web Proxy, able to "stop-and-modify" reques

From the top of my mind: 1. HTTP Request builder (think cURL with a nicer GUI and the ability to save presets); 2. Web Proxy, able to "stop-and-modify" requests (think Fiddler or Charles); 3. Network conditions simulator for throttling, packet dropping and limited bandwidth, with profiles (e.g. GPRS); 4. Local Mock REST API, with a few predefined endpoints (e.g. /users/) + the ability to create new ones (with configurable values such as random integers between X and Y or a random string which is a valid e-mail); 5. Multi-touch simulator (with a modifier key); 6. A usability test facilitator, able to create test scripts and automatically record timing and extra information (e.g. define a task that ends when user clicks the element with id X; when said user clicks #X, you annotate the time, the number of misclicks, etc). You could also implement this for static images, with clickable regions. I would love you for this one.

oib 12y ago
The second one is possible with the Tamper Data plugin: https://addons.mozilla.org/nl/firefox/addon/tamper-data/ https://addons.mozilla.org/nl/firefox/addon/tamper-data/
- geoka9 12y ago
  It would be very handy to be able to modify the payload of requests/responses as well without resorting to MITM proxy applications.
  - sergiosgc 12y ago
    Tamper Data is not a MITM proxy. It's a browser add on that modifies the request before the browser executes it.
jksmith 12y ago
Yeah on all this stuff.
dante9999 12y ago
I see that concerning point one and two there is option 'edit and resend' visible if you hover over request in network tab, and there is also option 'enable persistent logs', that shows what happens between refreshes. Don't know how it works, just playing around for 10 minutes. Overall I'm impressed with new network panel, much better than before.
- jimmyhmiller 12y ago
  That's pretty excited. Unfortunately when I try to edit and send a POST it gets changed to an option. Anyone know why?
  - sebasmagri 12y ago
    The OPTIONS request you're getting is probably just a preflight request related with CORS policies.
ndesaulniers 12y ago
The best channel for these suggestions is our user voice [0], or devtools bugzilla component [1] though lot's of Mozillian's hang out on HN (and subsequently ring vote themselves out of oblivion). [0] https://ffdevtools.uservoice.com/forums/246087-firefox-developer-tools-ideas https://ffdevtools.uservoice.com/forums/246087-firefox-devel... [1] https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer%20Documentation&component=Developer%20Tools https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer...
- paulojreis 12y ago
  I've replicated the suggestions in user voice. I'll share the link here, as HN readers may wish to vote for them: https://ffdevtools.uservoice.com/users/59733168-paulo-reis https://ffdevtools.uservoice.com/users/59733168-paulo-reis
geoka9 12y ago
Very nice list. I would also add the ability to associate breakpoints with DOM elements. As in "break on any attempt to read/modify a given element". That would be extremely helpful in debugging the hodge-podge of Javascript libraries that many modern web pages are.
- paulojreis 12y ago
  The break on modifications should already be possible, by adding breakpoints to Mutation Events (as you can do already with e.g. mouse related events). However, Mutation Events were marked as deprecated by allegedly bad design. We should be using MutationObserver[1] instead (which, I believe, will be equally helpful in observing changes). [1] https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver https://developer.mozilla.org/en-US/docs/Web/API/MutationObs...

oib 12y ago

The second one is possible with the Tamper Data plugin: https://addons.mozilla.org/nl/firefox/addon/tamper-data/ https://addons.mozilla.org/nl/firefox/addon/tamper-data/

geoka9 12y ago
It would be very handy to be able to modify the payload of requests/responses as well without resorting to MITM proxy applications.
- sergiosgc 12y ago
  Tamper Data is not a MITM proxy. It's a browser add on that modifies the request before the browser executes it.

jksmith 12y ago

Yeah on all this stuff.

dante9999 12y ago

I see that concerning point one and two there is option 'edit and resend' visible if you hover over request in network tab, and there is also option 'enable persistent logs', that shows what happens between refreshes. Don't know how it works, just playing around for 10 minutes. Overall I'm impressed with new network panel, much better than before.

jimmyhmiller 12y ago
That's pretty excited. Unfortunately when I try to edit and send a POST it gets changed to an option. Anyone know why?
- sebasmagri 12y ago
  The OPTIONS request you're getting is probably just a preflight request related with CORS policies.

ndesaulniers 12y ago

The best channel for these suggestions is our user voice [0], or devtools bugzilla component [1] though lot's of Mozillian's hang out on HN (and subsequently ring vote themselves out of oblivion). [0] https://ffdevtools.uservoice.com/forums/246087-firefox-developer-tools-ideas https://ffdevtools.uservoice.com/forums/246087-firefox-devel... [1] https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer%20Documentation&component=Developer%20Tools https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer...

paulojreis 12y ago
I've replicated the suggestions in user voice. I'll share the link here, as HN readers may wish to vote for them: https://ffdevtools.uservoice.com/users/59733168-paulo-reis https://ffdevtools.uservoice.com/users/59733168-paulo-reis

geoka9 12y ago

Very nice list. I would also add the ability to associate breakpoints with DOM elements. As in "break on any attempt to read/modify a given element". That would be extremely helpful in debugging the hodge-podge of Javascript libraries that many modern web pages are.

paulojreis 12y ago
The break on modifications should already be possible, by adding breakpoints to Mutation Events (as you can do already with e.g. mouse related events). However, Mutation Events were marked as deprecated by allegedly bad design. We should be using MutationObserver[1] instead (which, I believe, will be equally helpful in observing changes). [1] https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver https://developer.mozilla.org/en-US/docs/Web/API/MutationObs...