Logging full XHR requests when developer tools isn't open

[jes...@gmail.com]

Are there any plans to enable a developer feature to track XHR
requests even when the developer tools window isn't open? This used to
be the case if you had resource tracking 'always enabled' but now
chrome only tracks them if you have the inspector window open. You
have to reload the page if you forget to open the developer tools
window and it's quite frustrating when doing development.

I know that you can view the XHR requests (but not the full data) via
the use of the XHR logging in the console window (as pointed out to me
by pfeldman http://code.google.com/p/chromium/issues/detail?id=70705).

[pfeldman]

(Partially copying thread from the bug)

To get console entries for XHRs:
- Open DevTools
- Open console
- Invoke context menu
- check XHR logging button.
There entries are incomplete unless devtools window is opened (no
headers, no content).

We had to remove resource tracking option due to the poor usability of
the toggle and the memory overhead it was introducing (it was caching
all the resource metadata + now that we support raw headers and raw
timing, it all added up).

What is your scenario precisely? Would "hiding / minimizing" devtools
window work for you (i.e. open devtools, minimize it, work with the
page, restore devtools to see network data)? Hide/minimize seems to be
a popular request. We would really not like to store all the request
metadata, but if it ends up a popular request, we will definitely do
that. For that particular use case, you should file a separate bug at
crbug.com (with DevTools: prefix). Users will learn about it from
here, will star it and it will get into our priority queue. The more
details about your use cases you provide, the better!

Thanks
Pavel

[jstrx]

I'm developing a web application that does a whole bunch of AJAX
requests on loading the page. these ajax requests receive some JSON
from a backend, and i want to be able to view these JSON objects. With
the newly revamped developer tools, you first have to load the page,
then go to developer tools and reload the page in order to see XHR.

Say i have a form with 15 inputs. If I had to fill in this form
submit it, and had forgotten to open developer tools and want to see
what the form was sending to the backed/what the server returned, i
would first have to open developer tools, reverse whatever action the
form submit did and then retype those 15 inputs again and hit submit.
If i have say 5 - 10 tabs open, this means i then need to have 5 - 10
developer tools windows open as well if i want to see XHR across these
tabs.

If there was some per domain or per URL way of telling chrome to track
all the request metadata, this would save me (and i'm presuming
others) a heap of time and effort. The problem with the minimize
solution is you still have to remember to open developer tools every
single time you open a new testing tab.