[PL][morele.net] The CC expire year is not autofilled correctly
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://www.morele.net/
- Using autofill feature, hover over any saved CC entry to check the autofill preview.
- Select any CC entry in order to autofill the fields.
Expected result
- Form autofill should be applied on eligible fields with pre-saved information.
Actual result
- The CC expire date is not correctly autofilled, the year is populated with the first two digits, instead of the last two ones.
Regression range
- N/A
Additional notes
- Can't confirm the behavior on Chrome, due to a card verification warning.
- On preview the CC expire date shows four digits, instead of two.
- fathom fox sample
Updated•2 years ago
|
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Probably need to check whether we can improve our heuristic in
creditCardExpiryDateTransformer
and creditCardExpMonthAndYearTransformer
to fix this issue.
Comment 2•1 year ago
|
||
Fixed by Bug 1822385
Comment 3•1 year ago
|
||
I can still reproduce this issue in the latest Nightly 116.0a1 (2023-07-03). The expiry date is autofill correctly if the autofill is triggered from the CC number or name fields, but if you try to autofill from the expiry date field, the wrong date format is displayed.
Comment 4•1 year ago
|
||
(In reply to Alin Ilea, Desktop QA from comment #3)
I can still reproduce this issue in the latest Nightly 116.0a1 (2023-07-03). The expiry date is autofill correctly if the autofill is triggered from the CC number or name fields, but if you try to autofill from the expiry date field, the wrong date format is displayed.
When users click on the expiry date field, the websites remove the MM/RR
label, which makes our heuristic loses the hint to infer what format to fill. That is why when the autofill is triggered from the other fields, the issue doesn't exist (We can see the label in this case).
Hi Alin, could you help file another bug for this issue and keep this bug as verified (We autofill the right format when the autofill is triggered from fields other than expiry field)? Thanks!
Comment 5•1 year ago
|
||
Sure thing, marking this accordingly and keeping track of the expiry year wrong format in bug 1841615.
Description
•