搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Feature Suggestion: Default container option in Multi-Account Containers

more options

Hi,

I would find it very useful to be able to designate a default container (which could be "No Container") for sites that are not already assigned to a container. In other words, with this feature, if a link is opened from a page in container X, but the link does not have a container associated with it, the tab would open in the default container rather than container X. To give a concrete example: My Google searches & news are in a Google container. When I click a search result, e.g., from a news organization that I don't visit enough to make a container for, I'd prefer it did not open in the Google container, but a different, generic one or No Container.

I realize there could be some odd side-effects if a site spans multiple domains or hosts if they're not all marked for one container, but as an optional feature I think it wouldn't bother people who don't want to deal with that possibility.

Another way to do something similar would be to allow users to mark a container as "exclusive," meaning any link not in the sites assigned to that container would automatically go to No Container in the absence of an assignment. These two options also be implemented and work together.

Apologies if this is the wrong place to post this or if there's already a way to do this that I just haven't found. Thanks for any help!

-j

Hi, I would find it very useful to be able to designate a default container (which could be "No Container") for sites that are not already assigned to a container. In other words, with this feature, if a link is opened from a page in container X, but the link does not have a container associated with it, the tab would open in the default container rather than container X. To give a concrete example: My Google searches & news are in a Google container. When I click a search result, e.g., from a news organization that I don't visit enough to make a container for, I'd prefer it did not open in the Google container, but a different, generic one or No Container. I realize there could be some odd side-effects if a site spans multiple domains or hosts if they're not all marked for one container, but as an optional feature I think it wouldn't bother people who don't want to deal with that possibility. Another way to do something similar would be to allow users to mark a container as "exclusive," meaning any link not in the sites assigned to that container would automatically go to No Container in the absence of an assignment. These two options also be implemented and work together. Apologies if this is the wrong place to post this or if there's already a way to do this that I just haven't found. Thanks for any help! -j

所有回复 (1)

more options

Hi jef, You might find this interesting:

Default container https://github.com/mozilla/multi-account-containers/issues/356

and elsewhere on the Support Site: mozilla /multi-account-containers https://github.com/mozilla/multi-account-containers/issues