For now, with Fission and devtools.contenttoolbox.fission turned on, we do not log correctly console messages that are done early in two cases:

• when we navigate to a page loaded in another process than the current one (you would also need to toggle devtools.target-switching.enabled pref to test that)
• when an iframe, loaded from another origin, loads in a distinct process.

To address that would need to do a few things first:

• support additional frame targets (bug 1593937). For now we don't support attaching correctly to iframe added after we opened the devtools.
• resource API (bug 1576624). This will allow creating the actors very early, when the frame starts loading and depend on the previous bullet. This will also simplify listening for a given resource on all the targets we care about, without having to attach to each individual target.

Note: we could tweak devtools/client/webconsole/test/browser/browser_webconsole_inspect_cross_domain_object.js to cover early messages.

Tracking Fission DevTools bugs for Fission Nightly (M6) milestone

dt-fission-m2-reserve bugs do not need to block Fission Nightly (M6). For now, let's track them for Fission riding the trains to Beta (M7) so we revisit these bugs before we ship Fission.

Bulk move of all dt-fission-m2-reserve bugs to Fission MVP milestone.

Moving "dt-fission-m3-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.