How do I edit domains for multi-account containers?
Digging through documentation a bit, I haven't been able to find how to edit the list of domains set to always open in specific containers. Is there a good way to do this? My primary use case is for domains which quickly redirect you elsewhere, e.g. to track statistics on external links from a site.
Alle Antworten (9)
Hi, as there is now a lot of Container Extensions out there and also can turn it on with some code it would be great if you told us what the name was.
If it was this one :
You will find a Video on the page Further information :
Thanks for your help! I am using the addon you had linked. Specifically what I'm looking to do is manually edit the list of domains for which "Always open in $container" is checked, to add domains which will redirect the user away before they get the chance to check that box.
The closest-looking file I've found is "~/.mozilla/firefox/$PROFILE.default/browser-extension-data/@testpilot-containers/storage.js", which seems to have a mapping between domains & containers, but I'm not sure that's the right file (or if there's not a better-supported way of editing the list)
Hi, that would be a appropriate file as to if there are others no idea. Though would see if you wanted to go to 3 Bar Menu --> Help --> Submit Feedback and suggest that more info be out in the Support Article and a Team will review it.
Answer Back so someone that knows the answer will let yo know or not.
Thanks for your help! Ideally I'm looking for a UI option if one is available, but documentation on the structure of that file would be helpful as well.
You would have to use the Debug button on the about:debugging page to get access to the storage used by the extension. This will open the Browser Toolbox and you need to enable this toolbox to be able to gt this work.
Thanks! Oddly enough, the debugger that comes up gives me "No data present for selected host" in all Storage subsections, regardless of whether the page I have open in the main Firefox window is on a domain connected to a container. Do you know if there are additional steps needed?
I've attached a screenshot of the local storage section, as a glance at assignManager.js hints that that's the right section (although to be honest my Javascript is relatively weak, so I may be wrong)
(actually attaching the screenshot)
to clarify a bit , the storage.js file I mentioned above has many entries like:
"siteContainerMap@@_www.youtube.com":{"userContextId":"9","neverAsk":true}
so it isn't that the state is actually empty
looking a bit more in-depth at the file, it doesn't look incredibly complex - at this point I'm mostly just looking for any guardrails I can give myself over manually adding a bunch of `"siteContainerMap@@_$DOMAIN": {"userContextId": "$CONTAINER", "neverAsk":true}`, e.g. in case there's special character encoding needed for domains.