In various cases, we would need to act early when the process/frame/worker (i.e any target) has just been created. For example, very early when the document just starts loading to a new URL. Or as soon as the worker starts, just before we start evaluating its Javascript.

We would need to act early in order to:

• fetch the very first console messages
• same for network events
• register breakpoints before any JS executes

Tracking DevTools bugs for Fission Nightly (M6) milestone

Adding dt-fission whiteboard tag to DevTools bugs that mention Fission or block Fission meta bugs but don't already have a dt-fission whiteboard tag.

Moving these DevTools Fission bugs from Fission's old M6 Nightly milestone to M7 Beta. I am assuming these bugs would have the dt-fission-m2-mvp whiteboard tag if they were Fission Nightly blockers.

Bulk change of all bugs with whiteboard tag of dt-fission to Fission MVP milestone.

Once all dependent bugs are closed, the watcher actor will support all target type, and we can remove some workaround code I'm about to introduce via bug 1678385 in the ResourceWatcher.

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