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
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