Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Why does Google Maps always open outside a container (looping endless)

  • 1 reply
  • 0 have this problem
  • 2 views
  • Last reply by Vexi

more options

I tried to add maps.coogle.com to a specific container. this ends opening maps forparts of a second in this container displaying the cookie content page. regardles if a agree or not, it opens the cookie consent page in a new tab (looping forever) is there a way to add a site to a specific container using a config file? is here a way to add a site to a container, without having the subsites after the TLD, in the URL

Kind regards

I tried to add maps.coogle.com to a specific container. this ends opening maps forparts of a second in this container displaying the cookie content page. regardles if a agree or not, it opens the cookie consent page in a new tab (looping forever) is there a way to add a site to a specific container using a config file? is here a way to add a site to a container, without having the subsites after the TLD, in the URL Kind regards

All Replies (1)

more options

Hi! 👋 This is a fairly common issue when adding maps.google.com to a specific Firefox container. Here is some information that may help you:

1. Google Maps opens in the container, then loops with the cookie page This phenomenon often occurs when:

Subdomains like consent.google.com, ogs.google.com, etc. are not included in the same container

Sites redirect to other domains/subdomains that are not associated with the container

Cookies are not shared between containers, which is why the consent confirmation is not saved

Solution: Try adding all subdomains (e.g. consent.google.com) to the same container manually. Unfortunately, the Multi-Account Containers extension does not currently support asterisks (*.google.com).

2. Can I add a page to a container via a configuration file? There is no official way to configure containers via an external file. However, there is an experimental procedure via about:debugging and the extension's internal storage:

Find "Multi-Account Containers" and click Inspect 1. Open about:debugging → "This Firefox" 2. Find "Multi-Account Containers" and click Inspect 3. In the console, type: let data = await browser.storage.local.get(); data["siteContainerMap@@_google.com"] = data["siteContainerMap@@_maps.google.com"]; delete data["siteContainerMap@@_maps.google.com"]; await browser.storage.local.set(data); Warning: This can break your settings if not done correctly. I recommend saving your container data beforehand. I hope this helps! Vexi

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.