You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating System + Version: Arch Linux version 5.16.10-arch1-1
Firefox Version: 97.0.1
Other installed Add-ons + Version + Enabled/Disabled-Status: Happens without any other add-ons installed
Actual behavior
Containers filter by host name only. For example: if I add www.google.com/android/find to a container that stores cookies for my Google account, multi-account-containers assigns all URLs with the hostname of www.google.com to that container. This is undesirable because it means all my searches through google.com will automatically be redirected into that Google container.
Desired behavior
Containers can be instructed to filter by specific paths (optionally, URL patterns in general). This could be an option when adding the website to a container, while editing a container's site list, or both. Paths and subdomains are often used interchangeably (e.g. maps.google.com vs google.com/maps), and multi-account-containers does filter by specific subdomains, so it should be able to filter by paths as well.
Actual behavior
Containers filter by host name only. For example: if I add www.google.com/android/find to a container that stores cookies for my Google account, multi-account-containers assigns all URLs with the hostname of www.google.com to that container. This is undesirable because it means all my searches through google.com will automatically be redirected into that Google container.
Desired behavior
Containers can be instructed to filter by specific paths (optionally, URL patterns in general). This could be an option when adding the website to a container, while editing a container's site list, or both. Paths and subdomains are often used interchangeably (e.g. maps.google.com vs google.com/maps), and multi-account-containers does filter by specific subdomains, so it should be able to filter by paths as well.
Notes
Alternatively, adding a site to a container could automatically base itself on the full path, so that if I select "Always open this site in" while at www.google.com/android/find, it would assign only www.google.com/android/find to a container. In order to add www.google.com to a container, I would need to select "Always open this site in" while specifically at www.google.com. In that case, website resolution might be based on starts-with, so www.google.com includes anything on www.google.com (including www.google.com/android/find), but www.google.com/android/find only includes www.google.com/android/find/*.
The text was updated successfully, but these errors were encountered: