Multi-account-containers: [Feature request] list websites associated with container

[ricab]

Sometimes I want to "always open a website in a container", but choose the container with this other related website. Or I want to check what sites are potentially going to be exposed to this each other in a container.

For that I would have to see what sites I assigned to which containers. I could not find a way to do that today.

[lhorace]

Hey there,

Or I want to check what sites are potentially going to be exposed to this each other in a container.

This could be checked now, albeit obscure, click on MAC -> Edit Container -> Pencil of the container, from here you should see a list of assigned sites.

For that I would have to see what sites I assigned to which containers. I could not find a way to do that today.

That would be nice, though, may not be human readable, you could have a look at the json file for the time being?

[ricab]

Ah I see, thanks. Where can I find the json file?

[lhorace]

.mozilla/firefox/<profilename>/containers.json and .mozilla/firefox/<profilename>/browser-extension-data/@testpilot-containers/storage.js. The latter is difficult to read.

[ricab]

OK, I have storage.js.migrated here, which does not seem to have the current session's info yet. But I could indeed see some sites associated with container id's in the second file and then lookup the container ids->names in the first. clang-format made it easier to read the jsons :)

I think I'll stick with the first method you proposed. Thank you!

[stoically]

Starting with Firefox 66 the Add-on storage is automatically migrated to IndexedDB (hence the storage.js.migrated file). It's now located in .mozilla/firefox/<profile>/storage/default/moz-extension+++<Internal UUID>^userContextId=4294967295. The Internal UUID for a given Add-on can be obtained from about:debugging. A way to get more or less human readable local storage would be:

• Navigate to about:debugging
• Tick Enable add-on debugging
• Click on Debug under the Add-on name
• Confirm the dialog
• In the Console type browser.storage.local.get().then(console.log)
• Check the returned Object