This is probably going to require coordination with the Devtools team.

• Investigate why browser_ext_devtools_network.js is disabled under fission, if it depends on web extensions framework, the devtools team or just the test itself.

Tracking DevTools bugs for Fission dogfooding milestone (M5).

Extension devtools API doesn't need to block Fission dogfooding (M5). Tracking for Fission Nightly (M6).

Netmonitor is still missing remote frame requests or doesn't handle cross process navigation quite right.
So that the DevTools API you are using over here:
https://searchfox.org/mozilla-central/source/browser/components/extensions/parent/ext-devtools-network.js#47-52
May not work for remote frame or if there is a cross process navigation.

Bug 1663523 is the last big piece preventing this to work. But this will only enabled just after in bug 1665383.

Bug 1663523 is the last big piece preventing this to work. But this will only enabled just after in bug 1665383.

In that case, I'll make this bug depend on bug 1663523 and bug 1665383.

Those bugs are currently in the Fission M7 and MVP milestones, respectively. In which Fission milestone does this bug belong?

Tracking these DevTools test bugs for Fission Beta milestone (M7).

According to zombie, this shouldn't block beta experiment (M7) but will block shipping on beta so moving to MVP.

(In reply to Neha Kochar [:neha] from comment #7)

According to zombie, this shouldn't block beta experiment (M7) but will block shipping on beta so moving to MVP.

Moving from MVP to M7a because M7a is the next Beta milestone.

Tentatively assigning to zombie.

Adding a few devtools/extensions related bugs for tracking purposes, and moving to a more appropriate milestone.

I expected we'll have more work on our end for this meta, but turns out most of the fixes are happening on the devtools side. Still keeping me assigned to keep track of dependencies and follow up if needed.

Adding dt-fission whiteboard tag to note that this is a DevTools bug and doesn't need to block shipping Fission MVP.

This bug is assigned to Fission Milestone M8, but has whiteboard tag dt-fission instead of dt-fission-m3-mvp.

I'm adding the dt-fission-m3-triage tag so DevTools Fission triage can decide whether this bug should be fixed for dt-fission-m3-mvp or can be postponed from Fission Milestone MVP to Future.

Removing triage whiteboard tag as meta bugs are not included as part of the project's MVP backlog. If there are individual dependencies which should be considered the whiteboard tag can be added to them.

Moving this meta bug from Fission M8 to Future because the remaining blocking bugs are themselves tracked for Fission M8 or Future.

We don't have tests disabled for fission anymore:
https://searchfox.org/mozilla-central/search?q=fission&path=components%2Fextensions%2F**.ini

And the two remaining bugs blocking this are more something we would want to do than necessary blocking extensions/devtools from working with Fission, and can be tracked independently. Closing as fixed.