Closed
Bug 1838255
Opened 3 years ago
Closed 3 years ago
The default Fingerprinting Protection target doesn't get enabled in Fingerprinting Protection is enabled.
Categories
(Core :: Privacy: Anti-Tracking, defect, P2)
Core
Privacy: Anti-Tracking
Tracking
()
RESOLVED
FIXED
116 Branch
| Tracking | Status | |
|---|---|---|
| firefox116 | --- | fixed |
People
(Reporter: timhuang, Assigned: timhuang)
References
Details
Attachments
(1 external file)
The default fingerprinting protection targets doesn't get enabled if fingerprinting protection is enabled.
It's because the default value will be skipped if the pref privacy.fingerprintingProtection.overrides is empty. We should still populate the default list if the pref is empty.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Privacy: Anti-Tracking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Component: General → Privacy: Anti-Tracking
Product: Firefox → Core
| Assignee | ||
Comment 2•3 years ago
|
||
We won't add the default fingerprinting protection targets if the
override pref is empty. This is undesirable, we should still add the
default RFPTargets in this case.
Pushed by tihuang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/439d02859a2e
Keep processing fingerprinting override even if the override pref is empty. r=tjr
Comment 4•3 years ago
•
|
||
Oh, good find! I think we could also initialize the atomic with the default value.
// Actually enabled fingerprinting protections.
-static Atomic<uint32_t> sEnabledFingerintingProtections;
+static Atomic<uint32_t> sEnabledFingerintingProtections(kDefaultFingerintingProtections);
Comment 5•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox116:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•