Title: Allow Domains to be Associated with Groups of Containers

[grating5491]

Description:
Currently, the Multi-Account Containers extension lets a user assign a single container to a specific domain. While this is useful for automatic rerouting, it falls short for users who maintain multiple contexts for the same domain (for example, multiple work or personal accounts on a single site).

I propose adding a domain-to-container-group feature. This would allow users to assign a domain to multiple containers within a group, rather than just one. When visiting the domain, the extension could:

1. Prompt the user to select which container in the group to use, or

2. Automatically choose a container based on a configurable preference (e.g., most recently used, default container).

Benefits:

• Users can easily manage multiple contexts per domain.

• Maintains the convenience of automatic container routing.

• Reduces friction for users with complex browsing setups, such as separate accounts for work, personal, or side projects.

Example Use Case:

• Domain: example.com

• Container Group: Example containers

• Containers in Group: Work container, Play container

• Visiting example.com could prompt the user to choose which container to open, or default to the last container used in the group.

Suggested Implementation:

• Introduce a container group concept in the settings.

• Allow domains to be associated with multiple containers via these groups.

• Optionally, remember the last container used in a group for automatic routing.

• Provide a clear UI for selecting containers when multiple options exist.

[Jon]

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.