[PL][duka.com] No autofill functionality works on Name fields, while the preview for rest of the fields is restricted to their individual selection
Categories
(Toolkit :: Form Autofill, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox111 | --- | disabled |
People
(Reporter: asoncutean, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [fxcm-cc-new-geo])
Attachments
(2 files)
Found in
- 111.0
Affected versions
- 111.0
Affected platforms
- Windows 10
Preconditions
- browser.search.region = PL
- extensions.formautofill.creditCards.supportedCountries = PL
- Have at least one CC already saved
Steps to reproduce
- Reach the payment form on https://duka.com/pl
- Click on any of the Cardholder name fields to observe autofill dropdown
- Click on the Expire date and hover over any CC entry
- Press Enter
Expected result
- Form autofill/preview/clear should be applied on eligible fields.
Actual result
- Form autofill/preview/clear are not available for the First Name and Last Name fields.
- The preview is limited to the selected field (Card Number and Expire date).
Regression range
- N/A
Additional notes
- Not reproducible on Chrome.
- fathom fox sample
Updated•2 years ago
|
Updated•2 years ago
|
Comment 3•1 year ago
|
||
This should be fixed by Bug 1840584
Reporter | ||
Comment 4•1 year ago
|
||
The most part of the issue is fixed. But the autofill is no longer working for the expiry date field. Should i filled a separate issue for this matter and mark this one as verified?
Comment 5•1 year ago
|
||
(In reply to Anca Soncutean, Desktop QA from comment #4)
The most part of the issue is fixed. But the autofill is no longer working for the expiry date field. Should i filled a separate issue for this matter and mark this one as verified?
Hi Anca, thank you for verifying the bug. Yes, please file a new bug, thanks!
BTW, The issue you mentioned has the same root cause as Bug 1844364.
Reporter | ||
Comment 6•1 year ago
|
||
I've let a comment in 1844364 to address the the expiration date field separately. Based on the previous verification, from comment 4, I will mark this issue as verified fixed.
Description
•