Set optInPartitioning = true #140
AnotherUser321/librewolf-settings:set-optinpartitioning into master Could you also add network.cookie.cookieBehavior.optInPartitioning.pbmode
optInPartitioning.pbmode only seems to matter when the normal pref is false. I can still add it but that's why I intentionally left it out
github.com/mozilla-firefox/firefox@cea5f8cacb/netwerk/cookie/CookieService.cpp (L1072-L1080)
github.com/mozilla-firefox/firefox@cea5f8cacb/netwerk/cookie/CookieParser.cpp (L698-L706)
github.com/mozilla-firefox/firefox@cea5f8cacb/netwerk/cookie/CookieCommons.cpp (L494-L501)
@AnotherUser321 wrote in #140 (comment):
optInPartitioning.pbmodeonly seems to matter when the normal pref isfalse. I can still add it but that's why I intentionally left it out
github.com/mozilla-firefox/firefox@cea5f8cacb/netwerk/cookie/CookieService.cpp (L1072-L1080)github.com/mozilla-firefox/firefox@cea5f8cacb/netwerk/cookie/CookieParser.cpp (L698-L706)github.com/mozilla-firefox/firefox@cea5f8cacb/netwerk/cookie/CookieCommons.cpp (L494-L501)
I would still add it in case the behavior would change upstream
Not required while the non-pbmode pref is true, but set in case upstream changes.
I'd like to know why this is necessary. According to https://searchfox.org/firefox-main/source/modules/libpref/init/StaticPrefList.yaml#14302 the only thing this does is that it Changes cookieBehavior=5 to block third-party cookies by default.
network.cookie.cookieBehavior is already set to 5 by default. I may have looked over something, so in this case please do educate me, but otherwise it looks to me like it's yet another unnecessary change to explicitly set something that doesn't need to be set.
Edit
Ah, it actually makes sense now I read Changes cookieBehavior=5 from dynamic partitioning to block-by-default with opt-in. (https://searchfox.org/firefox-main/source/docs/_addons/etp_matrix.py#84).
The description from the first comment was ambiguous (when reading to as in order to).
That said, won't this break a lot of stuff, which is exactly why dynamic partitioning was made?
@ltguillaume wrote in #140 (comment):
That said, won't this break a lot of stuff, which is exactly why dynamic partitioning was made?
We used to have this set until a certain someone removed it. It would depend on how far sites have gotten in supporting CHIPs, which I have no idea about.
https://developer.mozilla.org/en-US/docs/Web/Privacy/Guides/State_Partitioning#storage_access_heuristics is still enabled, which would help reduce breakage.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?