Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Søg i 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.

Læs mere

Firefox Multi-Account Containers | Is it possible to "limit to designated" no matter what is the subdomain?

more options

When I'm using Firefox Multi-Account Containers with the option "Limit to designated sites" enabled, I encounter an annoying issue when navigating between different subdomains of the same website.

For example, if you navigate from "https://www.google.com" to "https://accounts.google.com," you will exit the "Google" container until that subdomain is manually added to the container.

I thought it would be nice if I could somehow create a container for "https://*.google.com/" (where * acts as a wildcard, as explained in the note below).

  • Is it possible to do this? If so, how, and what is the safest way? (See note below)
  • If not, is there any viable solution to this problem?

Note: The RegEx (or wildcard) * should only allow alphanumeric variations to prevent security vulnerabilities. For instance, "https://www.PhishingSite.com/WeStealYourAccount.google.com" could bypass the container if * is not restricted properly. In this case, * could mistakenly refer to "www.PhishingSite.com/WeStealYourAccount"

Thank you for your help

When I'm using Firefox Multi-Account Containers with the option "Limit to designated sites" enabled, I encounter an annoying issue when navigating between different subdomains of the same website. For example, if you navigate from "https://www.google.com" to "https://accounts.google.com," you will exit the "Google" container until that subdomain is manually added to the container. I thought it would be nice if I could somehow create a container for "https://*.google.com/" (where * acts as a wildcard, as explained in the note below). * Is it possible to do this? If so, how, and what is the safest way? (See note below) * If not, is there any viable solution to this problem? Note: The RegEx (or wildcard) * should only allow alphanumeric variations to prevent security vulnerabilities. For instance, "https://www.PhishingSite.com/WeStealYourAccount.google.com" could bypass the container if * is not restricted properly. In this case, * could mistakenly refer to "www.PhishingSite.com/WeStealYourAccount" Thank you for your help

Alle svar (3)

more options

Neat idea! I think you may have better luck posting this suggestion on GitHub.

Hope that helps -- Ed

Nyttig?

more options

Edward Sullivan said

Neat idea! I think you may have better luck posting this suggestion on GitHub. Hope that helps -- Ed

Sure thing,

I posted it here: Idea suggestion on GitHub

Thanks!

Ændret af tomerva22+2nd5wg4l den

Nyttig?

more options

Edward Sullivan said

Neat idea! I think you may have better luck posting this suggestion on GitHub. Hope that helps -- Ed

Sure thing,

I submitted an Idea suggestion on GitHub

Thanks!

Nyttig?

Stil et spørgsmål

Du skal logge ind på din konto for at svare på et indlæg. Start et nyt spørgsmål, hvis du ikke har en konto endnu.