-
Notifications
You must be signed in to change notification settings - Fork 63
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
Does not work with Firefox Multi-account containers #56
Comments
I don't think our extension can affect this. Either whitelist it (or the domains) if possible, or raise an issue to Firefox devs. |
Yes it's still not possible as far as I know, the extension itself doesn't run in the container, thus any requests don't have your session cookies. If someone think it's possible to fix, PRs are welcome. |
You can actually open extension pages in a container. Any moz-extension:// url can be opened in a container. I don't think that'll help much for the SteamDB extension since it doesn't even have a page that displays in a tab and it probably won't solve the cookie problem. |
I just did a little test and I managed to open a moz-extension:// page in a tab, right click on the tab |
Here is the official documentation for the API for Firefox Containers: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Work_with_contextual_identities I don't know if there is something there that would easily allow solving this issue. But I found this forum post that suggested a possible workaround, with this pull request on a different extension implementing it. |
Firefox Multi-Account Containers extension separates website storage into tab-specific Containers.
I am using to keep my browsing patterns separate.
While "Sign in Via Steam" feature of Steam Database extension works inside containerized tab. The browser extension is unable to retrieve game data. Since the browser extension uses cookies stored outside the containers.
Expected behavior:
The extension should use some other method to authenticate with steam. Maybe a login page for the extension itself.
The text was updated successfully, but these errors were encountered: