We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

საიტის გასაუმჯობესებელი სამუშაოების მიმდინარეობისას, შესაძლებლობების ნაწილი შეიზღუდება. თუ სტატიით ვერ მოახერხებ ხარვეზის გამოსწორება და შეკითხვის დასმა გსურთ, ჩვენი მხარდაჭერის გუნდი დაგეხმარებათ @FirefoxSupport გვერდის მეშვეობით Twitter-ზე და /r/firefox განყოფილებაში Reddit-ზე.

ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

Feature Suggestion: Default container option in Multi-Account Containers

  • 1 პასუხი
  • 1 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 1 ნახვა
  • ბოლოს გამოეხმაურა user104147805413306348376805769878442569366

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)

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