Closed Bug 1727316 Opened 4 years ago Closed 4 years ago

ClearDataService cleaners over-clear for non user requests

Categories

(Toolkit :: Data Sanitization, defect, P1)

defect

Tracking

()

RESOLVED FIXED
93 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox-esr91 --- wontfix
firefox91 --- wontfix
firefox92 --- wontfix
firefox93 --- fixed

People

(Reporter: emz, Assigned: emz)

References

(Regression)

Details

(Keywords: regression)

Attachments

(2 files)

Cleaners which can't delete by principal or base domain fall back to clear all. This is intended for cases where the user triggered the data clearing, so we don't leave data behind. However, if we call the ClearDataService programmatically, we don't want to over-clear. It can lead to bugs like Bug 1721084 where we clear state unrelated to the origin/baseDomain passed.

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 93 Branch

Is this something we should consider taking on ESR91?

Flags: needinfo?(pbz)

Unless we see more bugs like Bug 1721084, where we break due to over-clearing, I don't think we need to uplift to ESR for now.
(For Bug 1721084 we uplifted a separate fix)

Flags: needinfo?(pbz)
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: