Turn on Total Cookie Protection for all channels (phase 4)
Categories
(Core :: Privacy: Anti-Tracking, enhancement)
Tracking
()
People
(Reporter: Mardak, Assigned: emz)
References
Details
Attachments
(1 file)
Bug 1776760 - Enable dFPI by default for Beta and Release via cookieBehavior pref. r=#anti-tracking!
48 bytes,
text/x-phabricator-request
|
dmeehan
:
approval-mozilla-beta+
dmeehan
:
approval-mozilla-esr102+
|
Details | Review |
Currently behavior is 5 only in nightly (bug 1628486) but probably all channels in 103+ replacing the previous default of 4 (nightly bug 1492563, all bug 1525727)
This is the next phase after rolling out TCP via nimbus to 100% bug 1767384.
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Comment 1•3 years ago
|
||
[Tracking Requested - why for this release]: Current desire is to turn on Total Cookie Protection in 103 as "100%" nimbus rollout should be done during 102
Updated•3 years ago
|
Reporter | ||
Comment 2•3 years ago
|
||
[Tracking Requested - why for this release]: We want to turn this on for ESR 102.1 at the same release timeframe as 103
Comment 3•3 years ago
|
||
The bug is marked as tracked for firefox103 (beta). However, the bug still isn't assigned.
:timhuang, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit auto_nag documentation.
Comment 4•3 years ago
|
||
Paul will be working on this.
Assignee | ||
Comment 5•3 years ago
|
||
Comment 7•3 years ago
|
||
bugherder |
Comment 8•3 years ago
•
|
||
:pbz anything else blocking a beta uplift request on this and also on the regressions bug 1777501 and bug 1777513?
Assignee | ||
Comment 9•3 years ago
|
||
Comment on attachment 9283434 [details]
Bug 1776760 - Enable dFPI by default for Beta and Release via cookieBehavior pref. r=#anti-tracking!
Beta/Release Uplift Approval Request
- User impact if declined: This pref flip is the last stage of the Total Cookie Protection rollout (phase 4). We're already enabling TCP for almost 100% of release clients via our staged Nimbus rollout.
Rollout plan: https://docs.google.com/document/d/1Bs8Hh2YsEsDMfR2D9IePMV_RgrIjgo0etvfYwYtUhQQ/edit#
Telemetry Dashboard: https://sql.telemetry.mozilla.org/dashboard/tcp-global-rollout - 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: This is part of https://mozilla-hub.atlassian.net/browse/QA-1484
- List of other uplifts needed: Bug 1777501, Bug 1777513
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Low risk, since this is a simple pref flip. We've already rolled out TCP by default to over 80% of release users via Nimbus.
- String changes made/needed:
- Is Android affected?: No
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: As part of the global Total Cookie Protection rollout we also want to flip the TCP pref for ESR. We are already targeting ESR 102 with our Nimbus rollout.
- User impact if declined: See beta uplift request
- Fix Landed on Version: 104
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): See beta uplift request
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 10•3 years ago
|
||
No further blockers. See uplift request above.
Comment 11•3 years ago
|
||
Comment on attachment 9283434 [details]
Bug 1776760 - Enable dFPI by default for Beta and Release via cookieBehavior pref. r=#anti-tracking!
Approved for 103.0b6, thanks.
Comment 12•3 years ago
|
||
bugherder uplift |
Updated•3 years ago
|
Updated•3 years ago
|
Comment 13•3 years ago
|
||
Comment on attachment 9283434 [details]
Bug 1776760 - Enable dFPI by default for Beta and Release via cookieBehavior pref. r=#anti-tracking!
Approved for 102.1esr.
Comment 14•3 years ago
|
||
bugherder uplift |
Comment 15•3 years ago
|
||
This enhancement was part of the work done on QA-1484 and QA-1558 for which we sent green sign-offs. Considering this, I am marking it as Verified.
Description
•