Links should open in the Default Workspace (and assigned container, if set) instead of the last used one

[Shape6253]

Captchas

• I have read the instructions.
• I have searched existing issues and avoided creating duplicates.
• I am not filing an enhancement request.

What happened?

Currently, when opening external links (e.g., links from PDF files or other applications), Zen Browser opens them in the last active workspace instead of the default workspace. This behavior can be inconvenient for users who want all external links to be consistently opened in the default or a specific workspace. Additionally, if the current workspace has an assigned container, the external link does open in this container.

Using Temporary Containers with Automatic Mode does not fix this issue, as the external link still opens in the last used workspace rather than the expected default workspace with the assigned or temporary container.

Expected Behavior:

External links should open in the default workspace or in a dedicated, user-specified workspace.

Steps to Reproduce:

1. Open Zen Browser and create multiple workspaces.
2. Select a non-default workspace.
3. Open a link from a PDF file or another application.
4. The link opens in the last used workspace instead of the default one.

Proposed Solution:

• Add an option in the settings to choose whether external links should open in the default workspace or the last active workspace.
• Ensure that if a workspace has an assigned container, external links open within that container.
• If Temporary Containers (Automatic Mode) is enabled, external links should properly follow the isolation rules of the temporary container system.

This feature would improve usability and provide a more predictable experience for users who frequently work across multiple workspaces. Additionally, it would enhance privacy, especially in cases where certain containers—such as those for banking websites or other sensitive data—need to remain isolated.

Would love to hear if this is something that can be implemented or if there's a workaround. Thanks!

Reproducible?

• I have checked that this issue cannot be reproduced on Mozilla Firefox.

Version

1.9.1b

What platform are you seeing the problem on?

macOS - aarch64

Relevant log output if applicable