Copy data policy preferences between profiles in a group
Categories
(Toolkit :: Startup and Profile System, enhancement, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox138 | --- | verified |
People
(Reporter: jhirsch, Assigned: jhirsch)
References
(Depends on 2 open bugs, Blocks 4 open bugs, Regressed 1 open bug)
Details
(Whiteboard: [fidefe-profile-management])
Attachments
(2 files)
Updated 6 March 2025 with final scope for MVP release:
For each of the checkboxes in the "Data Collection and Use" section in about:preferences#privacy, including the crash reports checkbox (for now), we want to propagate any changes made in one profile to the rest of the profiles in the profile group. (That is, we'll need to include these prefs in our list of shared prefs.)
We'll also want to include the prefs that are set when users agree to the terms of service, which are the datareporting.policy prefs listed here: https://searchfox.org/mozilla-central/rev/d5cbb5b26c2fe8639da9ea0b0f225018d3697c59/modules/libpref/init/all.js#3734-3743.
To avoid any future gaps in legal compliance, we should also add a warning note to that prefs file (libpref/init/all.js) to remind anyone who adds policy prefs in the future to also add them to the SelectableProfileService list of shared prefs.
We're also going to add a sentence to the privacy section of about:preferences to explain that changes to these settings are applied to other profiles. See screenshot for specifics (taken from the Figma on 6 March). We'll need this extra sentence to be hidden unless the profiles feature is enabled.
To implement passing preferences around between profiles in a group, it should be enough to add the full list of data collection prefs to the initialSharedPrefs list in the SelectableProfileService, https://searchfox.org/mozilla-central/source/browser/components/profiles/SelectableProfileService.sys.mjs#109.
Note that the crash reports checkbox is disabled by default. The more privacy-centric approach would be to keep it per-profile, but we've heard from UX that the simpler approach (copy around all the data collection prefs) is easier for users to understand and the better approach at least until we make more involved settings changes prior to the profiles 100% release later this year.
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•11 months ago
|
||
Mass setting S2 severity for 0.5% release bugs. Apologies for the bug spam!
Comment 2•11 months ago
|
||
If we're syncing data choices across profiles we need to also sync the "new" profileGroupId when opting in.
Updated•10 months ago
|
| Assignee | ||
Comment 3•10 months ago
|
||
Clearing assignment--this is not yet ready to work; we are waiting on product to confirm the final behavior with legal and other PMs affected by propagating the unenrollment prefs across profiles in a group.
We have confirmed with legal that our fix does not need to ship with the other ToS changes in 136, because we are starting our rollout soon thereafter in 138.
| Assignee | ||
Comment 4•8 months ago
|
||
Copying over a comment from emilyw on slack:
Copy is approved and now in Figma here
Request to update SUMO for 138 is here: bug 1952062
| Assignee | ||
Updated•8 months ago
|
| Assignee | ||
Updated•8 months ago
|
| Assignee | ||
Comment 5•8 months ago
|
||
| Assignee | ||
Updated•8 months ago
|
| Assignee | ||
Comment 6•8 months ago
|
||
Also add an explanatory note to preferences.
| Assignee | ||
Updated•8 months ago
|
Comment 8•8 months ago
|
||
| bugherder | ||
Comment 9•7 months ago
|
||
Verified as fixed on Windows 11 and macOS 13.2.1 using Fx 138.0b2.
Description
•