Typo in browserglue pref. checkbox not depended on pref.
Categories
(Toolkit :: Form Autofill, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox126 | --- | unaffected |
firefox127 | + | verified |
firefox128 | + | verified |
People
(Reporter: epopescu, Assigned: ssachdev)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(2 files, 2 obsolete files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
Found in
- Firefox 127.0b4
Affected versions
- Firefox 127.0b4
Tested platforms
- Affected platforms: Windows10, macOS 11
Preconditions
- set pref browser.search.region = US in about:config
- install an older build than 127.0b4
Steps to reproduce
- Go to Help > About Firefox and restart browser
- Go to about:config and search pref extensions.formautofill.creditcards.reauth.optout
Expected result
- The pref extensions.formautofill.creditcards.reauth.optout doesn't hold any string because the "Require device sign in to fill and manage payment methods" checkbox is checked after updating the browser.
Actual result
- The pref extensions.formautofill.creditcards.reauth.optout holds encrypted string value after updating the browser.
Regression range
- N/A
Reporter | ||
Updated•9 months ago
|
Assignee | ||
Updated•9 months ago
|
Assignee | ||
Updated•9 months ago
|
Assignee | ||
Comment 1•9 months ago
|
||
Assignee | ||
Comment 2•9 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D211043
Updated•9 months ago
|
Updated•9 months ago
|
Updated•9 months ago
|
Comment 3•9 months ago
|
||
beta Uplift Approval Request
- User impact if declined: OS Auth setting wont be preserved.
- Code covered by automated testing: no
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: N/A
- Risk associated with taking this patch: None
- Explanation of risk level: A typo change
- String changes made/needed: None
- Is Android affected?: no
Comment 5•9 months ago
|
||
When I r+'d this I didn't realize this was in a migration.
Uplifting to beta will work for people who have not yet run this migration, but any existing beta users will have already set the pref with the "wrong" capitalization, and incremented the UI migration version, and so the migration will not re-run.
Updated•9 months ago
|
Assignee | ||
Comment 6•9 months ago
|
||
Updated•9 months ago
|
Updated•9 months ago
|
Assignee | ||
Updated•9 months ago
|
Comment 8•9 months ago
|
||
The patch landed in nightly and beta is affected.
:ssachdev, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox127
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Comment 9•9 months ago
|
||
We have a new bug that solves the problem for Beta. So no this patch in specific will not need an uplift but Bug1898323 will need an uplift once landed.
Assignee | ||
Updated•9 months ago
|
Assignee | ||
Comment 10•9 months ago
|
||
Hey nevermind. We might need an uplift for this. We're still discussing. You'll have a decision by end of day.
Assignee | ||
Updated•9 months ago
|
Assignee | ||
Comment 11•9 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D211043
Updated•9 months ago
|
Comment 12•9 months ago
|
||
beta Uplift Approval Request
- User impact if declined: Wrong pref setting will be made. New pref will be created which is not handled.
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: NA
- Risk associated with taking this patch: minimal
- Explanation of risk level: minimal since we're only working with prefs.
- String changes made/needed: none.
- Is Android affected?: no
Updated•9 months ago
|
Updated•9 months ago
|
Comment 13•9 months ago
|
||
uplift |
Updated•9 months ago
|
Updated•9 months ago
|
Reporter | ||
Comment 14•9 months ago
|
||
I've replicated this issue using Nightly 128.0a1 (2024-05-21) on macOS 11.
Verified as fixed in the latest Firefox 127.0 and Nightly 128.0a1 (2024-06-03) versions on Windows 10 x64 and macOS 11, as the issue no longer occurs.
Description
•