Bug 1821604 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

**Found in**
* 111.0-candidates

**Affected versions**
* 111.0-candidates

**Tested platforms**
* Affected platforms: Windows 10

**Preconditions**
* browser.search.region = IT
* extensions.formautofill.creditCards.supportedCountries = IT

**Steps to reproduce**
1. Reach the payment form on https://www.goldengoose.com
2. Fill in manually new CC info and submit the form

**Expected result**
1. The Credit Card save doorhanger should be displayed and capture all the expected fields: Cardholder Name, CC number (****last 4 digits).
 2. The credit card should be saved and stored with all the expected info: card number, cardholder name, expiration date, card type.


**Actual result**
1. Only the credit card number was captured and displayed in the doorhanger. The cardholder name wasn't captured.
 2. Only the credit card number and CC type is saved in the newly saved CC entry from the storage.


**Regression range**
* N/A

**Additional notes**
* The issue isn't reproducible on Chrome.
**Found in**
* 111.0-candidates

**Affected versions**
* 111.0-candidates

**Tested platforms**
* Affected platforms: Windows 10

**Preconditions**
* browser.search.region = IT
* extensions.formautofill.creditCards.supportedCountries = IT

**Steps to reproduce**
1. Reach the payment form on https://www.goldengoose.com
2. Fill in manually new CC info and submit the form

**Expected result**
1. The Credit Card save doorhanger should be displayed and capture all the expected fields: Cardholder Name, CC number (****last 4 digits).
 2. The credit card should be saved and stored with all the expected info: card number, cardholder name, expiration date, card type.


**Actual result**
1. Only the credit card number was captured and displayed in the doorhanger. The cardholder name wasn't captured.
 2. Only the credit card number and CC type is saved in the newly saved CC entry from the storage.


**Regression range**
* N/A

**Additional notes**
* The issue isn't reproducible on Chrome.
* FATHOM: https://drive.google.com/file/d/1srMln6hXUjnl7-UzhJogiL1pYPSAvQaY/view?usp=share_link

Back to Bug 1821604 Comment 0