Bugzilla

Luca, we are facing one issue here. When we handle the `http-on-stop-request` even for blocked request - the request doesn't seem to have nsILoadContext associated.

Here is how we get the context:
https://searchfox.org/mozilla-central/rev/7d0c94a0e9a9fe1f83553f49b10128567d21709d/devtools/shared/webconsole/network-helper.js#248

We need the context to get the top frame (or parent window where the request is executed):
https://searchfox.org/mozilla-central/rev/7d0c94a0e9a9fe1f83553f49b10128567d21709d/devtools/shared/webconsole/network-helper.js#217

The top frame/parent window is used to figure out whether the request belongs to the debugged tab (where the Toolbox is opened) and whether we should display it in the Network panel.

here is the `matchRequest` function implemented:
https://searchfox.org/mozilla-central/rev/7d0c94a0e9a9fe1f83553f49b10128567d21709d/devtools/server/actors/network-monitor/network-observer.js#102

Do you see a way how to solve this or does this need a platform change?

Honza

Luca, we are facing one issue here. When we handle the `http-on-stop-request` event for blocked request - the request doesn't seem to have nsILoadContext associated.

Here is how we get the context:
https://searchfox.org/mozilla-central/rev/7d0c94a0e9a9fe1f83553f49b10128567d21709d/devtools/shared/webconsole/network-helper.js#248

We need the context to get the top frame (or parent window where the request is executed):
https://searchfox.org/mozilla-central/rev/7d0c94a0e9a9fe1f83553f49b10128567d21709d/devtools/shared/webconsole/network-helper.js#217

The top frame/parent window is used to figure out whether the request belongs to the debugged tab (where the Toolbox is opened) and whether we should display it in the Network panel.

here is the `matchRequest` function implemented:
https://searchfox.org/mozilla-central/rev/7d0c94a0e9a9fe1f83553f49b10128567d21709d/devtools/server/actors/network-monitor/network-observer.js#102

Do you see a way how to solve this or does this need a platform change?

Honza