dFPI rollout pref set to false should not always set cookie behavior to BEHAVIOR_REJECT_TRACKER
Categories
(Core :: Privacy: Anti-Tracking, defect, P1)
Tracking
()
People
(Reporter: emz, Assigned: emz)
References
Details
(Whiteboard: [fxatps-tcp])
Attachments
(1 file)
|
48 bytes,
text/x-phabricator-request
|
diannaS
:
approval-mozilla-beta+
|
Details | Review |
Setting privacy.restrict3rdpartystorage.rollout.enabledByDefault to false explicitly will always set cookie behavior to BEHAVIOR_REJECT_TRACKER. This is unexpected for release channels which have a different default cookie behavior.
Instead we should revert the cookie behavior to its initial default value.
| Assignee | ||
Comment 1•4 years ago
|
||
This behavior isn't problematic for now, since Beta and Release use BEHAVIOR_REJECT_TRACKER as the default. However, we should keep it in mind when we want to switch over to BEHAVIOR_REJECT_TRACKER_AND_PARTITION_FOREIGN by default. In that case opted-out users would get BEHAVIOR_REJECT_TRACKER.
| Assignee | ||
Comment 2•4 years ago
|
||
Comment 3•3 years ago
|
||
Feel free to raise up the priority if you feel needed.
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
Comment 5•3 years ago
|
||
Backed out for causing mochitest failures in browser_contentblocking_standard_tcp_toggle
Backout link: https://hg.mozilla.org/integration/autoland/rev/5e4fb69d25c44a6b06cba30c86fb6bf1ce068c95
| Assignee | ||
Updated•3 years ago
|
Comment 7•3 years ago
|
||
| bugherder | ||
Comment 8•3 years ago
|
||
The patch landed in nightly and beta is affected.
:pbz, is this bug important enough to require an uplift?
If not please set status_beta to wontfix.
For more information, please visit auto_nag documentation.
| Assignee | ||
Comment 9•3 years ago
|
||
Comment on attachment 9251118 [details]
Bug 1741597 - Revert cookie behavior to initial default value when dFPI rollout pref is set to false. r=timhuang!
Beta/Release Uplift Approval Request
- User impact if declined: This is part of the TCP / dFPI rollout. This bug impairs the rollout for specific users. If we want to switch users over to have dFPI enabled by default, but they still have an opt-out choice stored in their profile from the experiment, they'll not be switched over to dFPI until we remove the experiment / opt-in code.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: On Nightly:
- Go to about:config and verify
network.cookie.cookieBehavioris set to5initially - Add a bool pref
privacy.restrict3rdpartystorage.rollout.enabledByDefaultand set it totrue. =>network.cookie.cookieBehavioris still set to5 - Update
privacy.restrict3rdpartystorage.rollout.enabledByDefaulttofalse=>network.cookie.cookieBehavioris still set to5
On Beta:
- Go to about:config and verify
network.cookie.cookieBehavioris set to4initially - Add a bool pref
privacy.restrict3rdpartystorage.rollout.enabledByDefaultand set it totrue. =>network.cookie.cookieBehaviorhas changed to5 - Update
privacy.restrict3rdpartystorage.rollout.enabledByDefaulttofalse=>network.cookie.cookieBehavioris back on4
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Small code change with good test coverage.
- String changes made/needed:
| Assignee | ||
Updated•3 years ago
|
Comment 10•3 years ago
|
||
Comment on attachment 9251118 [details]
Bug 1741597 - Revert cookie behavior to initial default value when dFPI rollout pref is set to false. r=timhuang!
Approved for 100.0b8
Comment 11•3 years ago
|
||
| bugherder uplift | ||
Updated•3 years ago
|
Comment 12•3 years ago
|
||
Verified as fixed in our latest Beta 100.0b8 (64-bit) as well as our latest Nightly 101.0a1 (2022-04-19).
| Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Description
•