Skip to content
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

Site data cleared too aggressively in container tabs #2630

Open
2 tasks done
richardb64 opened this issue Mar 30, 2024 · 0 comments
Open
2 tasks done

Site data cleared too aggressively in container tabs #2630

richardb64 opened this issue Mar 30, 2024 · 0 comments
Labels
bug Something is broken!

Comments

@richardb64
Copy link

Before submitting a bug report

  • I updated to the latest version of Multi-Account Container and tested if I can reproduce the issue
  • I searched for existing reports to see if it hasn't already been reported

Step to reproduce

To reproduce, just use containers for their intended purpose, ie. as a way to isolate browsing between sites, or to enable multiple independent sessions on a single site.

All privacy-related general settings are set to default values (eg. delete-on-exit is not enabled).

Actual behavior

Browsing in containers seems to forget cookies and other site data faster than it should - it's hard to be specific, but certainly a lot quicker than the server-specified expiry would suggest. Data survives a simple browser restart, but in many ways containers seem to behave more like private tabs than normal tabs.

Additionally, and possibly related to the same underlying issue, "open frame in new tab" is losing site data, again in a way that doesn't happen for normal non-container tabs. It is as if the security profile (CORS, etc) is different between container and non-container tabs.

Expected behavior

Container tabs should behave in all respects identically to normal tabs, with the sole exception of site data being segregated. The lifetime of site data, and any security-related policies, should be identical to normal browsing.

Additional informations

I suspect that the problem here is actually in the Firefox core, since the Multi-Account Containers extension is essentially providing a GUI to otherwise hidden core functionality. If a Firefox bug therefore needs to be raised, then I can of course do that, though perhaps the extension devs will be in a better position to suggest specific areas of investigation.

Provide a copy of Troubleshooting Information page (optional)

No response

@richardb64 richardb64 added the bug Something is broken! label Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken!
Projects
None yet
Development

No branches or pull requests

1 participant