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)
Firefox
Profile Backup
Tracking
()
RESOLVED
FIXED
134 Branch
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.
Updated•1 month ago
|
Assignee | ||
Comment 1•1 month ago
|
||
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)
Comment 2•1 month ago
|
||
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)
Assignee | ||
Comment 3•16 days ago
|
||
Perfect, thanks!
Assignee | ||
Updated•16 days ago
|
Assignee: nobody → mconley
Assignee | ||
Comment 4•16 days ago
|
||
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
Comment 6•14 days ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 14 days ago
status-firefox134:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•