Hacker News Reader

Comment by SparkyMcUnicorn | Hacker News Reader

This doesn't work for me.

I have a "personal" container that I use for my Google/PayPal login, and sites that I use Google oauth with, same for a "work" container.

If each site used it's own container, I couldn't sign in with Google without signing in multiple times (let alone the mess of signing out old sessions, which I do once in a while).

View on HN

Google logins still work, this is a different kind of container from the Firefox container tabs.

I use this feature with container tabs and it's fine. There are so far one or two sites I've come across that this breaks, neither of them anything I care about.

For those curious about how this actually works: https://bugzilla.mozilla.org/show_bug.cgi?id=1330467

It doesn't work all the time. I tried it with Google login on Atlassian, it seems to rely on third-party cookies, and fails. There are a few bugs open on websites that don't work with this feature:

https://wiki.mozilla.org/Security/FirstPartyIsolation#First_...

I assumed it didn't work because it was an Atlassian site I was logging in with. Thanks for pointing this out.

Container tabs works for me very well, so I don't see much point in switching over and dealing with little bugs like this.

Atlassian actually rely on referrer headers as well! Extensions such as smart referrer break their single SSO system.

Sorry, are you using `privacy.firstparty.isolate` or container tabs? I think SparkyMcUnicorn was saying the former would not work for them.

Both. I'm saying they work together fine, and isolate works fine with Google logins. It's not that strict.

Reply on news.ycombinator.com