This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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.

ఇంకా తెలుసుకోండి

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

  • 2 ప్రత్యుత్తరాలు
  • 0 ఈ సమస్యలు కలిగి ఉన్నాయి
  • చివరి సమాధానమిచ్చినది tomerva22+2nd5wg4l

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

ప్రత్యుత్తరాలన్నీ (3)

more options

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

Hope that helps -- Ed

ఉపయోగపడిందా?

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!

న tomerva22+2nd5wg4l చే మార్చబడినది

ఉపయోగపడిందా?

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!

ఉపయోగపడిందా?

ఒక ప్రశ్న అడగండి

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