Vendor application-services with the credit card CVV update fix and clear CVVs on desktop with an empty string
Categories
(Toolkit :: Form Autofill, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox161 | --- | fixed |
People
(Reporter: dimi, Assigned: dimi)
References
Details
(Whiteboard: [fxcm-backlog])
Attachments
(2 external files)
Bug 2085717 changed the application-services autofill store so that update_credit_card keeps the stored CVV when cc_cvv is null, and clears it only when it is an empty string. Scrubbing encrypted data now also clears the CVV.
Desktop needs to:
- Vendor an application-services revision that includes that change.
- Pass an empty string instead of null from
jsRecordToUpdatableCreditCardFieldsinRustAutofillCreditCardStorage.sys.mjswhen a record has nocc-csc. Otherwise clearing a security code on desktop silently keeps the old one.
| Assignee | ||
Comment 1•19 days ago
|
||
Vendor application-services 53354393f, which merges #7687 (bug 2085717):
update_credit_card keeps the stored CVV when cc_cvv is null and clears it when
it is empty, and scrubbing encrypted data clears the CVV along with the number.
The revision also carries the upstream changes since eba864f9: Remote Settings
client errors include the server's error details (bug 1941569), ads-client
telemetry strings are cut to Glean's limit (bug 2047640), and
viaduct-backend-rust moves to reqwest 0.13.5 (bug 2084735).
This also includes the file changes from ./mach uniffi generate.
| Assignee | ||
Comment 2•19 days ago
|
||
The Rust store now keeps the stored CVV when an update passes null, so
clearing a security code on desktop has to pass an empty string.
The update doorhanger test pins existing behaviour: a form submitted with an
empty security code field keeps the stored one.
Depends on D337094
| Assignee | ||
Updated•19 days ago
|
Updated•19 days ago
|
https://hg.mozilla.org/mozilla-central/rev/9b24ca28bd1e
https://hg.mozilla.org/mozilla-central/rev/e32baf860048
Updated•5 days ago
|
Description
•