Closed Bug 1749613 Opened 2 years ago Closed 2 years ago

Allow rolling back TCP rollout

Categories

(Firefox :: Messaging System, enhancement)

enhancement

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox96 + wontfix
firefox97 + wontfix

People

(Reporter: Mardak, Unassigned)

References

Details

[Tracking Requested - why for this release]: This might want release 96 or beta 97 uplift depending on how urgent this rollout will happen.

Bug 1732271 originally added a new pref privacy.restrict3rdpartystorage.rollout.enabledByDefault that can be toggled by users through various nimbus-controlled UIs (spotlight message action bug 1738206 and about:preferences bug 1737565) to turn on Total Cookie Protection.

Currently, if the nimbus enrollment/rollout "experiment" is stopped, users who have opted in will still have the user set preference enabling TCP behavior (but won't see the messaging anymore). We want some way to roll users back to pre-TCP behavior.

andreio:

Flags: needinfo?(andrei.br92)

I don't think the nimbus feature check will work, the opt-in action will toggle the TCPToggleInStandard pref which is the fallback pref for tcpPreferences.enabled. Once a user opts in (ENABLE_TOTAL_COOKIE_PROTECTION_SECTION_AND_OPT_OUT), pref is set and isEnabled remains true even if experiment is ended (user pref value will take precedence even if experiment config is "off").

We could have a call for getExperimentMetaData(feature: tcp) where you suggested in BrowserGlue. Or alternatively we could register an tcpPreferences.onUpdate that does clearUserPref when the experiment is turned off.

I think we can enroll more users by using rollouts, they're available in 97.

Flags: needinfo?(andrei.br92)

We will favor user choice and accept leaving users who explicitly opted in to TCP as part of the rollout.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.