Workspace Specific Essentials to replace container specific essentials.

[gordonn]

Workspace specific essentials invalidates the need for containers. Workspace are in essence containers. Profiles also make containers even less useful. Having this extra layer of overhead can confuse users and isn't intuitive.

[100rab-S]

BTW, how to setup profiles in zen-browser? I need different profiles for work and personal so that I can have different extensions and accounts.

[vraravam]

open about:profiles and scroll/search for "Create new profile" button.

[vraravam]

Workspace specific essentials invalidates the need for containers. Workspace are in essence containers. Profiles also make containers even more useless. Having this extra layer of overhead can confuse users and isn't intuitive.

not necessarily. For those of us who like to have a single window (and thus a single profile), but at the same time, we want the sandboxing feature of containers, then the workspaces and containers are essential for this style of session management.

[gordonn]

Workspace specific essentials invalidates the need for containers. Workspace are in essence containers. Profiles also make containers even more useless. Having this extra layer of overhead can confuse users and isn't intuitive.

not necessarily. For those of us who like to have a single window (and thus a single profile), but at the same time, we want the sandboxing feature of containers, then the workspaces and containers are essential for this style of session management.

I was a bit unreasonable with my wording before. Having containers definitely has its use cases but giving the users an option to have workspace specific essentials without needing to use containers is reasonable.

[TheTrueWhiteOwl]

I would make it a dropdown with three options in order of complexity and customisability:

• the current default behaviour: shared essentials
• workspace specific essentials: more customisable since each workspace can be edited freely, lose the ability to share an essential across two workspaces
• container specific essentials: depending on what container you have assigned to each workspace the essentials are different, two workspaces with the same container share the essentials (would be cool if in order to expand on this containerless essentials would also be shared across all workspaces)

Problems I see:
Workspace specific essentials is basically already a thing due to pinned tabs. It can easily be recreated using the containers. You lose access to one of the differentiating features of essentials (they are basically tabs that are shared across workspaces)