Anti-tracking list in preferences mis-states what is being blocked when 3rd party restriction rollout pref is set
Categories
(Core :: Privacy: Anti-Tracking, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox107 | --- | affected |
People
(Reporter: Gijs, Unassigned)
References
Details
Attachments
(3 files)
Per discussion with Paul, filing this.
On beta 106, I'm seeing this list:
Standard
Balanced for protection and performance. Pages will load normally. Firefox blocks the following:
- Social media trackers
- Cross-site tracking cookies
- Cross-site cookies in Private Windows
- Tracking content in Private Windows
- Cryptominers
- Fingerprinters
Includes Total Cookie Protection, our most powerful privacy feature ever Total Cookie Protection contains cookies to the site you're on, so trackers can't use them to follow you between sites.
Paul says the cross-site bits are incorrect.
| Reporter | ||
Comment 1•3 years ago
|
||
Comment 2•3 years ago
|
||
Could you provide your about:support page for us to check if the prefs are in an incorrect stage? Thanks.
| Reporter | ||
Comment 3•3 years ago
|
||
I already provided this screenshot to Paul. Do you need something else? What, specifically?
Comment 4•3 years ago
|
||
We couldn't really reproduce this issue with a fresh profile. So, We were wondering if there are some prefs that interfere with the UI here, particular the rollout pref. So, I think it would be good if you could provide privacy.restrict3rdpartystorage.* prefs in a screenshot.
| Reporter | ||
Comment 5•3 years ago
|
||
These seem to also mostly be the default... Did you try to reproduce on beta rather than release or nightly?
Comment 6•3 years ago
|
||
Yeah, we did try Beta, release and nightly. It looks to me that you have the rollout pref set, which is privacy.restrict3rdpartystorage.rollout.enabledByDefault. And I can reproduce the same issue with the pref set.
| Reporter | ||
Updated•3 years ago
|
Comment 7•3 years ago
|
||
We have Bug 1776766 to remove this pref in Firefox 108, So I believe it will cover this case.
Comment 8•3 years ago
|
||
Thanks Tim! Our TCP rollout cleanup work should address this issue.
| Reporter | ||
Comment 9•2 years ago
|
||
The rollout pref seems to have gone away so I guess this can be closed?
Comment 10•2 years ago
|
||
Yes, thanks for the reminder.
Fixed as part of Bug 1776766.
Description
•