Doesn't work with Firefox's privacy.firstparty.isolate = true
See original GitHub issueWith privacy.firstparty.isolate = true
the cookie count is always zero and cookies are not deleted despite notification claiming that they were.
Details about the setting:
https://bugzilla.mozilla.org/show_bug.cgi?id=565965
https://www.torproject.org/projects/torbrowser/design/#identifier-linkability
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:48 (14 by maintainers)
Top Results From Across the Web
What breaks if you use First-Party Isolation in Firefox - Ctrl.blog
First-Party Isolation ( FPI ) is an optional privacy feature built-in to Firefox that enforces stricter security policies to block tracking ...
Read more >Doesn't work with Firefox's privacy.firstparty.isolate = true #75
With privacy.firstparty.isolate = true the cookie count is always zero and cookies are not deleted despite notification claiming that they were.
Read more >Security/FirstPartyIsolation - MozillaWiki
First Party Isolation - P2 (Target as Fx54 Aurora - 2017/3/6 ESR 52.0) ... launchWebAuthFlow doesn't work when privacy.firstparty.isolate is enabled ...
Read more >Provide an option for first-party isolation in Private Browsing ...
What do you mean Firefox behaves "normally"? Why would "privacy.firstparty.isolate" is true be PB mode only - how do I then use FPI...
Read more >Pocket doesn't work with privacy.firstparty.isolate set to true
With the pref: privacy.firstparty.isolate=true, clicking the pocket button on the toolbar will bring to getpocket.com and your list.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI: 1381197 - resolved fixed 59 an hour ago
Upstream Bug 1381197.