Temporary-containers: Per Domain Isolation Rules Debugging

[mkruer]

When using Per Domain Isolation rules, sometimes webpages you don’t expect will open up in a tmp container but the reason why is not obvious. It would be helpful if there was a way to see what rule(s) caused the page to open up in the tmp container. Perhaps if we could click on the tmp circle it could open up rules currently being used and other information?

[stoically]

Would indeed be helpful to have a debugger. Related: #104

Perhaps if we could click on the tmp circle it could open up rules currently being used and other information?

This particular UI is part of Firefox core and can't get modified by Add-ons.

[saj]

If you are particularly motivated to solve your problem, it is possible to get some feedback from the extension using the following workaround. This provided me with enough information to solve a problem with my per-domain isolation rules. Be warned that this feedback is verbose, and will impact perf.

1. Navigate to about:debugging.

2. On the left-hand side, click whichever button displays your list of installed extensions. (On Nightly, this button will read This Nightly.)

3. Click the Inspect button alongside the _Temporary Containers_ extension. A new inspector tab will open.

4. Click Console. Enter:

   window.log.DEBUG = true;

5. Try to reproduce your problem. The console should fill with debug messages from the extension.

6. Once you are finished with your testing, flip back over to the console and enter:

   window.log.DEBUG = false;

References:

• Debugging - Mozilla MDN
• src/background/log.js

[stoically]

FWIW, v1.0beta20 allows to exclude permanent containers and target domains globally, as well as disabling isolation globally with a button in the popup top-nav.

[maverick74]

@stoically does v1.0beta20 (and the versions that came after) got us closer to this bug's closure?

and what about #281? Does it help in anyway?

[stoically]

@maverick74 Nope