Closed Bug 1821651 Opened 2 years ago Closed 2 years ago

Remove privacy.clearsitedata.cache.enabled pref

Categories

(Core :: Storage: StorageManager, task, P3)

task

Tracking

()

RESOLVED FIXED
114 Branch
Tracking Status
firefox114 --- fixed

People

(Reporter: emz, Assigned: h.sofie.p)

References

Details

(Keywords: dev-doc-complete)

Attachments

(1 file, 1 obsolete file)

Bug 1671182 has shipped a while ago, we should remove the pref privacy.clearsitedata.cache.enabled pref which already defaults to false in release.

Note, if this goes in there are some docs implications. Minimally the pref needs to be removed from BCD for cache here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Clear-Site-Data#browser_compatibility

Keywords: dev-doc-needed
Assignee: nobody → hpeuckmann
Attachment #9324414 - Attachment description: WIP: Bug 1821651 - remove privacy.clearsitedata.cache.enabled from code base. r=pbz! → Bug 1821651 - remove privacy.clearsitedata.cache.enabled from code base. r=pbz!
Status: NEW → ASSIGNED
Pushed by hpeuckmann@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3ce125387ccb remove privacy.clearsitedata.cache.enabled from code base. r=pbz
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch

FF114 docs work for this can be tracked through https://github.com/mdn/content/issues/26246

See Also: → 1838506

A patch has been attached on this bug, which was already closed. Filing a separate bug will ensure better tracking. If this was not by mistake and further action is needed, please alert the appropriate party. (Or: if the patch doesn't change behavior -- e.g. landing a test case, or fixing a typo -- then feel free to disregard this message)

Comment on attachment 9437222 [details]
WIP: Bug 1821651 - Restore "Clear-Site-Data: cache" functionality r=pbz

Revision D228887 was moved to bug 1930500. Setting attachment 9437222 [details] to obsolete.

Attachment #9437222 - Attachment is obsolete: true

Accidentially put wrong bug number into patch. Correct Bug number is Bug 1930500.

See Also: → 1942272
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: