When navigating to another domain, DevTools will be broken because the target will be closed as a result of Bug 1617237. We should fix this.

Thanks for filing!

The following bug might be relevant here: Bug 1618695 - stop destroying TabDescriptor when navigating to another process. Once the TabDescriptor can survive across process change, we can also make the toolbox use a descriptor instead of a target and it could help to support target switching here.

Or we can implement a custom support for target-switching at https://searchfox.org/mozilla-central/rev/72e3388f74458d369af4f6cdbaeaacb719523b8c/devtools/client/framework/toolbox-init.js#139-148

Tracking Fission DevTools bugs for Fission Nightly (M6) milestone

Additional testing that should be done to ensure that debug target navigation survives a process change: we should make sure that navigation to about: pages from another external domain will not crash the tab. An example of this:

1. Go to https://www.wikipedia.org/ in another tab.
2. Open remote debugging for that particular tab.
3. In that same tab, go to about:robots

Right now, this will crash the tab remote debugging tab with an error: Cannot connect to the debug target. See error details below.

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.

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