Good news. As far as I understand, I can finally disable privacy.firstparty.isolate and disable the Facebook/Google container extensions, right? As long as I’m ok with Firefox’s heuristics that give the green light for partitioned storage access to the third parties I interact with, I don’t see how these extensions (and privacy.firstparty.isolate) would still be of any use with this new state partitioning management
I had some issues with cross-site logins and forms/videos not loading and sometimes it’s annoying. But I’ve never experienced really big issues because of FPI
Mmm… I don’t think so… firstparty.isolate do a lot of things. Actually with temporary container correctly configured you can think about turn it off, but IMHO it’s better to follow arkenfox user.js configurations. Actually, you can make your question on his github https://github.com/arkenfox/user.js/issues
So I went through this issue on arkenfox’s github that links to this bugzilla ticket. Judging from these two discussions, as far as I’ve been able to understand, it looks like dFPI does actually the same job of standard FPI, with some relaxed rules that trigger on interaction. So if you’re okay with the heuristics, you get the same level of partitioning from the two. Maybe I’m overseeing something
Good news. As far as I understand, I can finally disable
privacy.firstparty.isolateand disable the Facebook/Google container extensions, right? As long as I’m ok with Firefox’s heuristics that give the green light for partitioned storage access to the third parties I interact with, I don’t see how these extensions (andprivacy.firstparty.isolate) would still be of any use with this new state partitioning managementdeleted by creator
I had some issues with cross-site logins and forms/videos not loading and sometimes it’s annoying. But I’ve never experienced really big issues because of FPI
Mmm… I don’t think so… firstparty.isolate do a lot of things. Actually with temporary container correctly configured you can think about turn it off, but IMHO it’s better to follow arkenfox user.js configurations. Actually, you can make your question on his github https://github.com/arkenfox/user.js/issues
So I went through this issue on arkenfox’s github that links to this bugzilla ticket. Judging from these two discussions, as far as I’ve been able to understand, it looks like dFPI does actually the same job of standard FPI, with some relaxed rules that trigger on interaction. So if you’re okay with the heuristics, you get the same level of partitioning from the two. Maybe I’m overseeing something