Closed
Bug 1861442
Opened 1 year ago
Closed 1 year ago
[CA][www.bestbuy.ca]Name not captured in save address doorhanger when submitting the "New address" form
Categories
(Toolkit :: Form Autofill, task)
Tracking
()
VERIFIED
FIXED
121 Branch
Tracking | Status | |
---|---|---|
firefox121 | --- | disabled |
People
(Reporter: epopescu, Assigned: dimi)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [fxcm-addr-capture-ux])
Attachments
(2 files)
Found in
- Nightly 121.0a1
Affected versions
- Nightly 121.0a1
Tested platforms
- Affected platforms: Windows 10 x64, macOS 11
Preconditions
- Install the Firefox en-CA build
- Set browser.search.region to CA in about:config
- Flip following prefs in about:config:
extensions.formautofill.addresses.capture.v2.enabled = true
extensions.formautofill.addresses.supported = on - Use CA VPN to test
Steps to reproduce
- Log into https://www.bestbuy.ca/en-ca/ , add an item to bag and navigate to checkout page
- Fill in the Address Form and press the submit button
- Save the address through the Save address doorhanger
- Fill the "New address" form on the same checkout page and submit the form
Expected result
- All the details filled in the address form are captured in the save address doorhanger when the user fills the "New address" form.
Actual result
- The name is not captured in the save address doorhanger when user fills and submits the "New address" form.
Regression range
- N/A
Additional notes
- The issue can not be reproduced in Google Chrome.
- Fathom Fox page
Reporter | ||
Updated•1 year ago
|
Summary: [CA][https://www.bestbuy.ca]Name not captured in save address doorhanger when submitting the "New address" form → [CA][www.bestbuy.ca]Name not captured in save address doorhanger when submitting the "New address" form
Assignee | ||
Updated•1 year ago
|
Whiteboard: [fxcm-addr-capture-ux]
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee: nobody → dlee
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•1 year ago
|
||
It is quite common for the security code field to be located at the end of a credit card section.
This implies that if we have already encountered a security code field, the subsequent fields are unlikely to
be part of the credit card section.
Pushed by dlee@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5218fc7cf52b
Avoid updating fields to 'cc-name-*' if a security code field is already present in the reference credit card section r=jneuberger
Comment 3•1 year ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
Assignee | ||
Updated•1 year ago
|
Flags: qe-verify+
Reporter | ||
Comment 4•1 year ago
|
||
I've reproduced this issue using Nightly 121.0a1 (2023-10-27) on Windows10 x64.
Verified as fixed on the latest Nightly 121.0a1 (2023-11-09) version under same configuration where the issue no longer persists.
Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in
before you can comment on or make changes to this bug.
Description
•