New update checked "Cookies and site data" automatically for some users
Categories
(Toolkit :: Data Sanitization, defect, P1)
Tracking
()
People
(Reporter: dtsa583s0, Assigned: manuel)
References
(Blocks 1 open bug, Regression, )
Details
(Keywords: regression)
Attachments
(3 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
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.
Comment 1•18 days ago
|
||
:hsohaney, since you are the author of the regressor, bug 1888466, could you take a look?
For more information, please visit BugBot documentation.
Assignee | ||
Updated•14 days ago
|
Assignee | ||
Updated•14 days ago
|
Assignee | ||
Comment 2•14 days ago
|
||
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
Comment 3•14 days ago
|
||
Set release status flags based on info from the regressing bug 1888466
Assignee | ||
Comment 4•14 days ago
•
|
||
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.
Assignee | ||
Updated•14 days ago
|
Assignee | ||
Updated•14 days ago
|
Assignee | ||
Comment 5•14 days ago
|
||
Assignee | ||
Comment 6•14 days ago
•
|
||
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).
Updated•14 days ago
|
Assignee | ||
Comment 7•14 days ago
|
||
S2 fits better. Reflecting here in Bug.
Assignee | ||
Updated•14 days ago
|
Comment 8•14 days ago
|
||
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.
Assignee | ||
Comment 9•14 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D241037
Updated•14 days ago
|
Comment 10•14 days ago
|
||
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
Assignee | ||
Comment 11•14 days ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D241037
Updated•14 days ago
|
Comment 12•14 days ago
|
||
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
Comment 13•14 days ago
|
||
Comment 14•14 days ago
|
||
Backed out for causing browser_sanitizeDialog_v2.js.
Assignee | ||
Updated•13 days ago
|
Comment 15•13 days ago
|
||
Assignee | ||
Updated•13 days ago
|
Comment 16•13 days ago
|
||
bugherder |
Updated•12 days ago
|
Comment 17•12 days ago
|
||
uplift |
Updated•12 days ago
|
Updated•12 days ago
|
Comment 18•11 days ago
|
||
Reproduced the issue described in comments 2 and comment 10 using an update from Fx135 RC to Fx136 RC (affected). Verified that when updating from an old Nightly build 135.0a1 to latest Nightly 138.0a1 (fixed) only 2 options remain checked.
Before
[x] History
[ ] Cookies and site data
[ ] Temporary cached files and pages
[ ] Site settings
After:
[x] Browsing & Download History
[ ] Cookies & site data
[ ] Temporary cached files and pages
[x] Saved form info
[ ] Site settings
Is Saved from info supposed to be checked as well? If yes then I'll call this verified fixed on 138.0a1 and wait for beta 137.0b6 build to be out so I can verify that as well.
Assignee | ||
Comment 19•11 days ago
|
||
Yes, "Saved form info" is supposed to be checked after the update due to the previous "History" item also including form data clearing.
Updated•10 days ago
|
Comment 20•10 days ago
|
||
uplift |
Updated•10 days ago
|
Comment 21•8 days ago
|
||
(In reply to Manuel Bucher [:manuel] from comment #19)
Yes, "Saved form info" is supposed to be checked after the update due to the previous "History" item also including form data clearing.
Thanks! Marking as verified fixed on 138 and on Firefox 137 as well since I also tested right now across platforms (Windows 11, macOS 13.7 and Ubuntu 22.04) and looks fixed as well.
Leaving this as rezolved for now, waiting to also test in 136 Release.
Comment 22•7 days ago
|
||
Also verified that this is fixed after updating from 135.0.1 to 136.0.2 across platforms (Windows 11, macOS 13.7 and Ubuntu 22.04).
Description
•