Closed
Bug 1741437
Opened 3 years ago
Closed 3 years ago
When TCP is ON the Standard strings reflects the contrary
Categories
(Core :: Privacy: Anti-Tracking, defect, P3)
Core
Privacy: Anti-Tracking
Tracking
()
RESOLVED
WONTFIX
| Tracking | Status | |
|---|---|---|
| firefox96 | --- | affected |
People
(Reporter: sbadau, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
146.26 KB,
image/png
|
Details |
[Environment:]
All
Nightly 96.0a1
[Steps:]
- Open Nightly with a new profile
- Go to about:preferences#privacy and observe the trackers from about:preferences#privacy
- In about:config change privacy.restrict3rdpartystorage.rollout.preferences.TCPToggleInStandard to true so that the TCP checkbox is enabled
- Observe again the trackers from about:preferences#privacy
- Check the TCP checkbox and reload the Settings page
[Expected Result:]
After step 5, the strings for the TCP enabled should still be displayed:
- Social media trackers
- Cross-site cookies in all windows (includes tracking cookies)
- Tracking content in Private Windows
- Cryptominers
- Fingerprinters
[Actual Result:]
After step 5 the strings for TCP disabled are displayed.
- Social media trackers
- Cross-site tracking cookies
- Cross-site cookies in Private Windows
- Tracking content in Private Windows
- Cryptominers
- Fingerprinters
Updated•3 years ago
|
Priority: -- → P1
Comment 2•3 years ago
|
||
Lower the priority because this seems a Nightly-only bug. And Paul is aware of this issue.
Flags: needinfo?(pbz)
Priority: P1 → P3
Comment 3•3 years ago
|
||
I've confirmed that this issue is only reproducible on Nightly, not Beta. This is due to the default cookieBehavior value.
Nightly already has TCP enabled, and we're not targeting it with our rollout experiment.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•