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

privacy.partition.network_state & privacy.firstparty.isolate #1084

Closed
atomGit opened this issue Dec 30, 2020 · 2 comments
Closed

privacy.partition.network_state & privacy.firstparty.isolate #1084

atomGit opened this issue Dec 30, 2020 · 2 comments

Comments

@atomGit
Copy link

atomGit commented Dec 30, 2020

i searched issues and saw no relevant info so i hope i'm not repeating here, but why the new pref privacy.partition.network_state when we already have FPI?

and can these two be used in tandem (or should they be used in tandem)?

it seems like privacy.partition.network_state adds a couple things not covered by FPI, but i don't understand why this wasn't added to FPI or what the overlap between the to is

@rusty-snake
Copy link
Contributor

Maybe #1051 is your duplicate. See 07cccd5.


If privacy.partition.network_state=true and browser.cache.cache_isolation=true are useless if FPI=true but not if FPI=false. Why do we haven't them in something like FPI ALT?

@atomGit
Copy link
Author

atomGit commented Dec 30, 2020

i was wondering how privacy.partition.network_state got flipped to true in my user.js - that might be the answer - i'm pretty keen on running the cleaner script, but it looks like i missed a round - thanks

@atomGit atomGit closed this as completed Dec 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants