Open Bug 1952564 Opened 5 days ago Updated 11 hours ago

New update checked "Cookies and site data" automatically for some users

Categories

(Toolkit :: Data Sanitization, defect, P1)

Firefox 136
Desktop
Unspecified
defect

Tracking

()

Tracking Status
firefox-esr128 --- unaffected
firefox136 + affected
firefox137 + affected
firefox138 + affected

People

(Reporter: dtsa583s0, Assigned: manuel, NeedInfo)

References

(Regression, )

Details

(Keywords: regression)

Attachments

(3 files)

Steps to reproduce:

Some users are reporting that Firefox 136 checked the option to clear "Cookies and site data" automatically for them. This is likely a regression caused by Bug 1888466.

I was not personally affected by this, since I had already manually checked this option. Please reach out to those users if you need more info.

Component: Untriaged → Data Sanitization
Keywords: regression
Product: Firefox → Toolkit
Regressed by: 1888466
Hardware: Unspecified → Desktop

:hsohaney, since you are the author of the regressor, bug 1888466, could you take a look?

For more information, please visit BugBot documentation.

Flags: needinfo?(harshit.sohaney)

I'm able to reproduce upgrading one of my Nightlies upgrading from Fx132 to Fx138.

Before

  • [x] History (Clears site and download history, saved form info, and searches)
  • [ ] Cookies and site data (May sign you out of sites or empty shopping carts)
  • [ ] Temporary cached files and pages (Clears items that help sites load faster)
  • [ ] Site settings (Resets your permissions and site preferences to original settings)

After:

  • [x] Browsing & Download History
  • [x] Cookies & site data
  • [x] Temporary cached files and pages
  • [x] Saved form info
  • [ ] Site settings
Status: UNCONFIRMED → NEW
Ever confirmed: true

Set release status flags based on info from the regressing bug 1888466

Thanks for reporting!

I'll triage as:

  • P1 as in "Fix in the current release cycle". Not sure what potential solutions could look like
  • S2 as in Major functionality impaired. due to users being logged out unexpectedly

Will start investigating further. Feel free to downgrade if you disagree or if later information turns out this isn't as severe/important as thought. Due to workaround one could argue it is S3: "Blocks non-critical functionality or a work around exists".

Taking a look now.

Flags: needinfo?(harshit.sohaney)
Severity: -- → S2
Priority: -- → P1
Assignee: nobody → manuel

Bumping severity due cause of data loss for users that have clear data on shutdown activated. This is a potential dot release driver. Most noteable cookies and therefore logins. And less noticable cache and siteSettings. (not entirely sure if this is a correct assessment. please downgrade again to S2 if that is a better reflection of situation due to only a subset of users being affected and workaround existing).

Severity: S2 → S1

S2 fits better. Reflecting here in Bug.

Severity: S1 → S2
Priority: P1 → --
Priority: -- → P1

We've determined that this is not a dot release driver but we would ride along another dot release if it happens. It only affects a subset of users who have clear on shutdown enabled and the fix would only help users who have not updated to 136 yet.
Around 6% of all users have the feature enabled. Out of those 6% only those users are affected who have non default categories (selected or unselected), including the cookies and storage category.

See Also: → 1953240
Attachment #9471165 - Flags: approval-mozilla-beta?

beta Uplift Approval Request

  • User impact if declined: Users not updated to Fx136 yet might lose login data after update when having clear data on shutdown activated, but not clear cookies
  • Code covered by automated testing: yes
  • Fix verified in Nightly: no
  • Needs manual QE test: yes
  • Steps to reproduce for manual QE testing: Set the prefs in Fx135 like in https://bugzilla.mozilla.org/show_bug.cgi?id=1952564#c2, then update to Fx136. Observe the additional checkboxes. Also possible to replicate by fiddeling with about:config preferences.
  • Risk associated with taking this patch: low
  • Explanation of risk level: fairly simple patch and testing coverage exists. Some paths already additionally manually verified. But additionally should go through QE.
  • String changes made/needed: no
  • Is Android affected?: no
Flags: qe-verify+
Attachment #9471166 - Flags: approval-mozilla-release?

release Uplift Approval Request

  • User impact if declined: Users not updated to Fx136 yet might lose login data after update when having clear data on shutdown activated, but not clear cookies
  • Code covered by automated testing: yes
  • Fix verified in Nightly: no
  • Needs manual QE test: yes
  • Steps to reproduce for manual QE testing: Set the prefs in Fx135 like in https://bugzilla.mozilla.org/show_bug.cgi?id=1952564#c2, then update to Fx136. Observe the additional checkboxes. Also possible to replicate by fiddeling with about:config preferences.
  • Risk associated with taking this patch: low
  • Explanation of risk level: fairly simple patch and testing coverage exists. Some paths already additionally manually verified. But additionally should go through QE
  • String changes made/needed: no
  • Is Android affected?: no
Pushed by mbucher@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1c0dde7af6e9 Fix "Cookies and site data" being set for users when migrating from clear-site-data dialog v2 to v3 (unmerge history and formdata) r=emz

Backed out for causing browser_sanitizeDialog_v2.js.

Flags: needinfo?(manuel)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: