-
-
Notifications
You must be signed in to change notification settings - Fork 469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Temporary Containers Automatic Mode doesn't work on Zen Browser #172
Comments
This issue is stale because it has been open for 30 days with no activity. |
Does it still happen? |
yup still happen, same with Floorp and Librewolf as well |
It still occurs on Zen, but works normal for me on Librewolf |
it's probably the extension's fault then, no? |
@mauro-balades Screen.Recording.2024-10-13.at.19.02.43.mov |
I think I found a solution. Inspecting the Temporary Containers, you will immediately notice a lot of uncaught errors from Examining Temporary Containers source code, Setting I can't comment whether this fix breaks other container extensions. If they hardcoded checking cookieStoreId against |
What happened?
Temporary Containers Extension Issue
Extension Details
Issue Description
The Temporary Containers extension is designed to automatically assign new tabs to temporary containers when the "Automatic Mode" setting is enabled. This feature works as expected in regular Firefox up to the current Developer Edition as of now, even if the extension is outdated. However, when using the Zen browser the "Automatic Mode" feature doesn't work.
Steps to Reproduce
Expected Result
When opening a new tab in step 4, the Temporary Containers extension should automatically assign the tab to a temporary container.
Actual Result
When opening a new tab in step 4 in Zen Browser, the Temporary Containers extension does not automatically assign the tab to a temporary container.
Reproducible?
Version
Alpha build - 1.0.0-a.12
Severity impact
Medium, Enhancement
What platform are you seeing the problem on?
Linux, Windows
Relevant log output
No response
The text was updated successfully, but these errors were encountered: