Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

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

Opaite Mbohovái (3)

more options

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

Hope that helps -- Ed

¿Imba’eporãva?

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!

Moambuepyre tomerva22+2nd5wg4l rupive

¿Imba’eporãva?

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!

¿Imba’eporãva?

Eporandumína

Nde eikéke nde mba’etepe embohovái hag̃ua ñe’ẽmondo. Ikatúpa, emoñepyrũ peteĩ porandu, ndereguerekói gueteriramo nemba’ete.