[FEATURE REQUEST] With the feature of assigning workspaces to a website and assigning containers to a website, when we want to open the website URL, the website will open in the workspaces we assign and in the container we assign.

[universish]

🔢 🥇 💯 The feature I am talking about is that we can assign a Workspaces to a website. When we try to open the website, the website will open in the workspaces we have assigned. It will also open in the container we assigned to the website. If we have not assigned a container to the website, it will open in the container we assigned to the workspaces when we created the workspaces.

If the feature of assigning containers to workspaces is added (I created this feature request. This feature is available in Floorp browser).

For this feature to work, you first need to install the Firefox Multi-Account Containers plugin. Then you create a container for your workspaces. For example, you should create a git container for git websites (e.g. github gitlab etc.). When creating a new workspaces you assign a container for workspaces and create workspaces. You also change the name of workspaces to git. Then you open github in this workspaces. It automatically runs it in the container named git. This is a very useful feature.

Note: This is not the feature I requested in this issue. I have already created an issue for this feature request. In this issue, I am requesting another feature. The feature I am talking about here works together with the feature I mentioned in the previous feature request. See also: #2912

To assign a container to a website, we open the website without a container. Then left click on the “Always Open Site in Container” button created by the Firefox Multi-Account Containers add-on. Then we select the container we want to assign. The website opens in a new tab in that container. After that, every time we open the website, it will always open in that container.

🔢 The feature I am talking about is that we can assign a Workspaces to a website. When we try to open the website, the website will open in the workspaces we have assigned. It will also open in the container we assigned to the website. If we have not assigned a container to the website, it will open in the container we assigned to the workspaces when we created the workspaces.

This feature is very useful and improves security. It is also a very useful feature to increase security. We can easily prevent cross-site cookies.

Can you add this feature to zen-browser?

[kakato10]

I think that if you can assign a Profile to a Workspace, it would be enough to be able to assign a Workspace for a website to achieve the behavior you described

[Fxxxlei]

Maybe you are using the wrong terminology or mixing things up.
Profiles are not containers and you cannot assign profiles to workspaces, if anything it's the other way around.
But you can assign containers to wokspaces, you can set URLs to automatically open in specific containers with an extension (Firefox Multi-Account Containers) and you can configure that tabs should be moved to a workspace with their container assigned to it.

Combining those, I think this should cover the feature.