1730160 - Match content network requests on target exact window (and not on the window "tree" anymore) when we have same-origin iframe targets

Status: RESOLVED FIXED

(DevTools :: Netmonitor, task)

Description

[Nicolas Chevobbe [:nchevobbe]]

At the moment, when checking which requests should be sent to the client, we are checking if the window the request was emitted from belongs to the "target window tree" (see https://searchfox.org/mozilla-central/rev/1761c710b035d7dc8892dfa8e56589b4e095221f/devtools/server/actors/network-monitor/network-observer.js#109-120 for example)

With Bug 1685500, we'll have targets for each document, so we can do an exact match on the window instead, as requests from iframes will be included from the iframes targets.

Comment 1

[Nicolas Chevobbe [:nchevobbe]]

Attachment: Bug 1730160 - [devtools] Filter content network event against exact target browsingContext/window when EFT is enabled. r=bomsy.

When we create targets for every frame, we need to tighten our different filters
so requests/resources are duplicated (we would get them from both the top-level
target as well as from their iframe).

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/af80802b2175
[devtools] Filter content network event against exact target browsingContext/window when EFT is enabled. r=bomsy.

Comment 3

[Marian-Vasile Laza]

https://hg.mozilla.org/mozilla-central/rev/af80802b2175