Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Where is the settings/config file/data for Multi-Account Containers?

  • 2 respostas
  • 2 têm este problema
  • 26 visualizações
  • Última resposta por searchingformore

more options

I accidentally set a frequent website I use to always open in the wrong container. I do get the prompt about 'would you like to open this container in [wrong container]' and I click the option not to do so while also having checked the box that says to remember this decision, but the check box seems to do nothing. I've checked the box countless times to no effect. I seem to have permanently created this state which is highly frustrating. I don't want this site opened in any container. I have a lot of sites I've configured in what I'm terming here "wrong container" (though it's the correct for those other sites), so I don't want to have to delete the entire container to fix this problem.

I've had other problems with Multi-Account Containers (such as, tabs I've closed coming back like zombies after restarting Firefox; or Firefox seeming to forget that certain tabs were in containers and the act of clicking their tab to place them in the correct container causes them first to reload in the default of no container), but for now my biggest issue is not being able to remove a website from the "always open in wrong container" list. Where is the list of websites per container stored? Is this somewhere in the about:config or in a raw, human-readable file on my filesystem somewhere? How can I fix my problem without having to delete the container entirely?

I'm running FF 82.0.2 (64-bit) with Multi-Account Containers version 7.2.0 on Manjaro Linux version 20.2

I accidentally set a frequent website I use to always open in the wrong container. I do get the prompt about 'would you like to open this container in [wrong container]' and I click the option not to do so while also having checked the box that says to remember this decision, but the check box seems to do nothing. I've checked the box countless times to no effect. I seem to have permanently created this state which is highly frustrating. I don't want this site opened in any container. I have a lot of sites I've configured in what I'm terming here "wrong container" (though it's the correct for those other sites), so I don't want to have to delete the entire container to fix this problem. I've had other problems with Multi-Account Containers (such as, tabs I've closed coming back like zombies after restarting Firefox; or Firefox seeming to forget that certain tabs were in containers and the act of clicking their tab to place them in the correct container causes them first to reload in the default of no container), but for now my biggest issue is not being able to remove a website from the "always open in wrong container" list. Where is the list of websites per container stored? Is this somewhere in the about:config or in a raw, human-readable file on my filesystem somewhere? How can I fix my problem without having to delete the container entirely? I'm running FF 82.0.2 (64-bit) with Multi-Account Containers version 7.2.0 on Manjaro Linux version 20.2

Solução escolhida

The only readable file in the profile folder that is about containers is containers.json that stores some data in JSON format. Extensions like MAC store their data in indexedDB (storage/default) in a SQLite database and this data isn't really accessible apart from using the about:debugging page and click the Inspect button next to the extension and then go to Storage.


Ler esta resposta no contexto 👍 1

Todas as respostas (2)

more options

Solução escolhida

The only readable file in the profile folder that is about containers is containers.json that stores some data in JSON format. Extensions like MAC store their data in indexedDB (storage/default) in a SQLite database and this data isn't really accessible apart from using the about:debugging page and click the Inspect button next to the extension and then go to Storage.


Modificado por cor-el a

more options

Thank you so much! I found the Extension Storage per your guidance. I thought I was still screwed since it's using app-specific UUIDs, not the human-readable names, but I found that when you right click on each data entry, one of the options for deletion includes the domain name for that data entry in human-readable form. So I just right clicked down the list til I found the domain name and deleted that entry. I checked by opening a fresh tab of the impacted website and (as desired) it did not load in the "wrong container". Thank you! I was dreading have to delete that container. You saved me so much time/pain!