Bugzilla

I believe this should be moved ahead to M5.

Unlike other (most of the?) work the Fission team is doing to replace features and primitives with OOPIF-compatible ones, this is introducing a new API that other teams (at least WebExt and DevTools, possibly others) need to build on top of.

Since we're working in parallel toward the same M6 goal, and since several of the things we need to build on top of this api are themselves non-trivial, I don't think it's reasonable for all of that to happen in the same milestone.

New APIs need to "bake" for some time before they could be reliable used. After landing, they need to be documented, learned, tried, [used](https://bugzilla.mozilla.org/show_bug.cgi?id=1594131) and [misunderstood](https://bugzilla.mozilla.org/show_bug.cgi?id=1596187), [crashes found and fixed](https://bugzilla.mozilla.org/show_bug.cgi?id=1597965#c13) -- which I don't think is possible in the span of a couple of months (as the history has shown).

I believe this should be moved ahead to M5.

Unlike other (most of the?) work the Fission team is doing to replace features and primitives with OOPIF-compatible ones, this is introducing a new API that other teams (at least WebExt and DevTools, possibly others) need to build on top of.

Since we're working in parallel toward the same M6 goal, and since several of the things we need to build on top of this api are themselves non-trivial, I don't think it's reasonable for all of that to happen in the same milestone.

New APIs need to "bake" for some time before they could be reliable used. After landing, they need to be documented, learned, tried, [used](https://bugzilla.mozilla.org/show_bug.cgi?id=1594131) and [misunderstood](https://bugzilla.mozilla.org/show_bug.cgi?id=1596187), [crashes found and fixed](https://bugzilla.mozilla.org/show_bug.cgi?id=1597965#c13) -- which I don't think is possible in the span of a couple of months (as history has shown).