Fix baseline & convenience prefs being set to default values on startup
Categories
(Core :: Privacy: Anti-Tracking, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr128 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox140 | --- | unaffected |
| firefox141 | --- | unaffected |
| firefox142 | --- | verified |
People
(Reporter: leoliu, Assigned: leoliu)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Initially, when an ETP-strict user upgrades privacy.trackingprotection.allow_list.hasMigratedCategoryPrefs is used to ensure baseline and convenience exceptions are false by default. However, setPrefsToCategory in ContentBlockingPrefs runs on every startup, causing it to overwrite the prefs to their default values. We should do a check to make sure baseline and convenience are only updated when user switches ETP modes or interacting with the checkboxes, not on startup.
Comment 1•1 year ago
|
||
This affects Nightly only, but we need to fix it before beta.
Updated•1 year ago
|
| Assignee | ||
Comment 2•1 year ago
|
||
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Set release status flags based on info from the regressing bug 1970647
Comment 6•1 year ago
|
||
| bugherder | ||
Comment 7•1 year ago
|
||
We verified the fix using a treeherder build on macOS 13, Windows 11 and Ubuntu 22. We can't reproduce the issue anymore neither for restart or reopen.
Updated•1 year ago
|
Description
•