(In reply to Mike Kaply [:mkaply] from comment #4)
We can probably add an option or a shortcut to immediately open this new tab as a new new window (with or without chrome UI). Can you be more specific about the "issues" this workflow creates for you?
It's not an issue once it occurred to me to drag the tab out of Firefox into a new window.
But in general, when debugging extensions, it doesn't make sense to try to debug in the same window (especially when in a lot of cases, you are debugging page content).
We should put the addon debugger in a separate window even if it isn't a separate process.
Thanks for confirming, I was afraid some scenarios might still require to have a debugger in another Firefox instance :)
I think we should add a preference, which when set to true, would lead to open all debug targets in new windows rather than in new tabs (
devtools.aboutdebugging.open-target-in-window or similar).
We can then decide whether this preference should default to true, and if we need to surface it in the UI (maybe in the Setup page of about:debugging?)