Closed Bug 884382 Opened 7 years ago Closed 7 years ago

The network monitor requires a page reload before it starts recording

Categories

(DevTools :: Netmonitor, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: st3fan, Unassigned)

Details

STR:

1) Open some single-page Ajaxy app
2) Open the developer tools, switch to the Network Monitor
3) Invoke some actions in your app that trigger network requests

Expected:

Whatever happens in the browser is recorded and displayed.

Actual:

Nothing is recorded.

The Network Monitor requires a full page reload to trigger it. This interrupts my debugging session and my application state.

My request is that the Network Monitor just immediately starts recording when you open it. Like Chrome does.
This (theoretically) shouldn't be happening and I can't reproduce with your STR. I made a small web server that replies with something when receiving a GET request. The request is immediately shown in the network monitor without having to reload the page.

Please add more info so that I can reopen. Pointing to a URL or giving a small example of a server would be very helpful.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Are you sure that is not supposed to be happening? Because when I open the Network Monitor there is a label in there that says "Reload the page to see detailed information about network activity."
(In reply to Stefan Arentz [:st3fan] from comment #2)
> Are you sure that is not supposed to be happening? Because when I open the
> Network Monitor there is a label in there that says "Reload the page to see
> detailed information about network activity."

Yeah, I'm sure :)

The label is mostly cosmetic, and only present if there are no request yet. It's a bit hard to explain "Perform a network request to see it here", so we went for the more generic "Just reload the page and you'll likely see things". If you have a suggestion, I'd be really happy to change it.
Ah! So in my case my requests are all XHR. Maybe XHR simply does not trigger the recording?
(In reply to Stefan Arentz [:st3fan] from comment #4)
> Ah! So in my case my requests are all XHR. Maybe XHR simply does not trigger
> the recording?

Nope, XHRs should definitely appear in the netmonitor. We also have tests for this and I haven't heard of any other such reports, so you might have found an unexpected/unhandled case.
Apparently https://minion-dev.mozillalabs.com experiences these issues.
Ok what happens here is actually very different than what I reported.

It seems that as soon as I open the Network Monitor (with command-option-q) my app stops making periodic network calls.

It is easy to STR now:

1) Login to https://minion-dev.mozillalabs.com
2) Make sure you have an account and that you see at least some sites in the Sites & Scans overview that you get after logging in (ask me if you need an account)
3) Observe in the access log of the web server that the browser is calling /api/sites every second
4) Open the Network Monitor
5) Observe that the browser has stopped calling /api/sites periodically

When I switch to the Console, I see the following JS error:

[14:13:18.556] Use of attributes' specified attribute is deprecated. It always returns true. @ https://minion-dev.mozillalabs.com/static/js/angular.js:4005
[14:13:18.754] Use of getPreventDefault() is deprecated.  Use defaultPrevented instead. @ https://minion-dev.mozillalabs.com/static/js/jquery-1.9.1.js:3346
--
[14:13:37.170] TypeError: nextTick is not a function @ https://minion-dev.mozillalabs.com/static/js/angular.js:6774

I understand that these all point to application code, but this is triggered by opening the network monitor.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Mihai, I don't know what to make of this. Any clues?
Flags: needinfo?(mihai.sucan)
OS: Mac OS X → All
Priority: -- → P3
Hardware: x86 → All
I'm marking this invalid. Stefan, please reopen with proper steps to reproduce, version information of your browser and a URL to a site that exhibits the issue.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → INVALID
(In reply to Victor Porof [:vp] from comment #9)
> Mihai, I don't know what to make of this. Any clues?

Reading through the comments I can't be sure what is happening.

Stefan, does the web console exhibit the same behavior? If you open the web console do you see network logs without reloading the page? Also, does the web console break the nextTick() function that you pointed at.

The network monitor uses the same backend for network logging like the web console. Also we do not expect our tools to negatively impact the web page - you say it stops sending network requests when you open the netmonitor. That's pretty severe.

However, as Rob pointed out we need clear steps to reproduce the issue and we will investigate further. Thank you!
Flags: needinfo?(mihai.sucan)
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.