I don't think this is the ideal solution, because I'd imagine there are a population of users who just wouldn't consider the possibility that SameCon could Be an add-on. Especially if the community is split roughly down the middle.
I think yours is the ideal solution, making SameCon a configurable option, but having the default option be DefCon. That way, the privacy and security protections are the Default behavior, but a user has the option to change it Built In
* CTRL-T opens in DefCon
* Right-clicking a link and selecting "Open in New Tab" opens in SameCon
That's what I would expect the default behavior to be.
But, if you're someone who browses primarily using keyboard shortcuts, this just doesn't cut it.
https://github.com/mozilla/testpilot-containers/issues/245
"Opening a new tab from a container window opens a normal tab and not a
container tab"
I should note that the last comment on that issue was made in July, so I went ahead and commented asking about adding a setting to change the new-tab container inheritance behavior.Personally I would want tabs to be in the bozo container by default, unless I explicitly grant the website access to a trusted container, or something.
Extension makers will experiment and Firefox can choose from what gets learned.
Mixing different containers in the same window feels a bit awkward to me.
Unfortunately my suggestion of Ctrl+Shift+T is already taken.
It's a bit awkward although it works, until they get the CTRL+T solved.
Example: I contain google.com to a container called "Google", then I perform a Google search. I click a search link, and it opens in the Google container.
Ideally this would still use default. There is the option to right click every link, select "Open in Container" and then pick the default but it's not really optimal for two reasons: 1. Manual effort by the user 2. The link is to a redirector on Google's site, before it forwards to the third party site (though I guess I can live with this, its kind of outside scope of the feature).
So, really, I just want to pin a domain to a container. If I leave that domain, I want it to change containers.
I haven't been able to find a good way to do this automatically, with any of the configurable settings.
EG, if you open it within the Google container, your privacy is most exposed. Whether you have to right click and select 'Open in a different container' when following search or email links, or whether you can have the browser do this automatically, the end result is the same. You're following a Google link, so if they create a special one that tells them which result you clicked on, they still see it and know about it because it's on their domain.
But once you get to that third party domain, you're in a separate container instead of one filled with your own special Adsense cookies.
There are extensions you can use to remove Google's redirect link in their result page.
But this is kind of tangent to what I was trying to get across.
If one has goal is to contain a web property, giving them their own container but then keeping that container open when you leave their site is not really containment.
And maybe some hints during the second time you open a tab.
We had some original mock-ups with more settings, but they cluttered the introductory UI and seemed to only confuse people new to the concept.
Do you have any proof like a larger survey? I highly doubt that's a 50:50 request.
Why should one want to open a new tab in the default container with Ctrl-t? Ctrl-t is used and learned as a shortcut to open something (like a tab) in the current context. The current context would be not just your current browser window but also your current container. Ctrl-n would go more in your direction.
Would be great if we had sensible defaults without the need to get exensions.
Besides, do I need to get a Firefox account for this feature?
Why isn't this under Test Pilot?
It's a popular request; about as popular as everyone who wants Ctrl+T to open in the default container. :)
So, for our core experience we picked the default behavior that helps maximize the privacy and security protections of Containers.
The good news is that, with the contextualIdentities extension API (exclusive to Firefox!), add-on authors can make their own add-ons to change this behavior. Like Taborama is doing:
https://github.com/kesselborn/taborama
Check out https://developer.mozilla.org/Add-ons/WebExtensions/API/cont... for more info on making Container-aware extensions.