Open
Bug 1813120
Opened 3 years ago
Updated 9 months ago
[US][coach.com] Credit Card Save doorhanger is displayed upon form submit only after page refresh and the expiry date is not saved to the storage
Categories
(Toolkit :: Form Autofill, task, P3)
Tracking
()
NEW
People
(Reporter: ailea, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug, )
Details
Attachments
(1 file)
|
2.93 MB,
video/mp4
|
Details |
Found in
- 111.0a1 (2023-01-27)
Affected versions
- 111.0a1, 110.0b5, 109.0
Tested platforms
- Affected platforms: Windows 10, macOS 11, Ubuntu 20
Preconditions
- browser.search.region US
Steps to reproduce
- Reach the payment form on www.coach.com/
- Fill in manually new CC info and submit the form
Expected result
- Submitting the form with new CC info should trigger the Credit Card save doorhanger.
- Only the CC number (****last 4 digits) should be displayed in the CC save doorhanger, since the CC Name field doesn't exist.
- The credit card should be saved and stored with all the expected info: card number, expiration date, card type.
Actual result
- The CC save doorhanger is displayed only after a page refresh.
- The "undefined" is displayed in the CC Name place instead of empty space.
- Only the credit card number and CC type is saved in the newly saved CC entry from the storage. The expiry date is not saved.
Regression range
- Not a recent regression.
Additional notes
- The CC save doorhanger is not displayed at all in Chrome.
| Reporter | ||
Comment 1•2 years ago
|
||
Verified the issue number 2 and the "undefined" is not displayed anymore in the CC doorhanger when the name field doesn't exist (fixed in bug 1815400). Updated the summary accordingly.
Summary: [US][coach.com] Credit Card Save doorhanger is displayed upon form submit only after page refresh and "undefined" is displayed for CC name → [US][coach.com] Credit Card Save doorhanger is displayed upon form submit only after page refresh and the expiry date is not saved to the storage
Updated•9 months ago
|
Type: defect → task
You need to log in
before you can comment on or make changes to this bug.
Description
•