Closed Bug 1924095 Opened 1 month ago Closed 14 days ago

Backup regeneration is triggered by normal cookie deletion, not just user-triggered deletion

Categories

(Firefox :: Profile Backup, defect, P3)

defect

Tracking

()

RESOLVED FIXED
134 Branch
Tracking Status
firefox133 --- disabled
firefox134 --- fixed

People

(Reporter: mconley, Assigned: mconley)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fidefe-device-migration])

Attachments

(1 file)

Despite bug 1923125 landing, I'm still seeing frequent regeneration with the cookie-changed observer getting notifications about COOKIE_DELETED. It looks like our observer isn't correctly distinguishing between "natural" cookie deletions, and cookie deletions triggered by an explicit user action.

Hey Tim,

Do you happen to know if there's a way to determine if a cookie deletion was caused by the user, say, clearing cookies/site data in about:preferences vs a cookie being deleted naturally by a site?

Flags: needinfo?(tihuang)

I think you can check the nsICookieNotification.browsingContextId to know if it's from a site or not. It should be zero if the deletion is from the Chrome UI.

Flags: needinfo?(tihuang)

Perfect, thanks!

Assignee: nobody → mconley
Pushed by mconley@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/baa459e5df1f Don't regenerate backups when cookies are removed by the site. r=backup-reviewers,sthompson
Status: NEW → RESOLVED
Closed: 14 days ago
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: