Closed Bug 1821319 Opened 2 years ago Closed 1 year ago

[PL][morele.net] The CC expire year is not autofilled correctly

Categories

(Toolkit :: Form Autofill, defect, P2)

Firefox 111
Desktop
Windows 10
defect

Tracking

()

VERIFIED FIXED
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

  1. Reach the payment form on https://www.morele.net/
  2. Using autofill feature, hover over any saved CC entry to check the autofill preview.
  3. 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
Severity: -- → S3
Priority: -- → P2
Whiteboard: [fxcm-cc-new-geo]

Probably need to check whether we can improve our heuristic in
creditCardExpiryDateTransformer and creditCardExpMonthAndYearTransformer to fix this issue.

Fixed by Bug 1822385

Status: NEW → RESOLVED
Closed: 1 year ago
Flags: qe-verify+
Resolution: --- → FIXED
Attached video 2023-07-03_16h06_35.mp4

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.

Flags: needinfo?(dlee)

(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!

Flags: needinfo?(dlee) → needinfo?(ailea)

Sure thing, marking this accordingly and keeping track of the expiry year wrong format in bug 1841615.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
Flags: needinfo?(ailea)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: