Open Bug 1657657 Opened 4 years ago Updated 4 years ago

[gap.com] CC Autofill does not work correctly

Categories

(Toolkit :: Form Autofill, defect, P3)

Desktop
All
defect

Tracking

()

Tracking Status
firefox79 --- disabled
firefox80 --- disabled
firefox81 --- affected

People

(Reporter: ailea, Unassigned)

References

(Blocks 2 open bugs, )

Details

(Whiteboard: [cc-autofill-reserve])

Attachments

(1 file)

Attached video Issue recording

Affected version:

Fx80 and FX81 - if CC specific prefs are enabled

Tested on:

Windows 10

Steps to reproduce:

  1. Have 1 CC profile saved
  2. Reach the payment form for https://www.gap.com/
  3. Click on the "Credit Card Number" field from the Payment Method section.

Expected Result:

The credit card autofill drop down should be opened.

Actual Result:

The credit card autofill drop down is not displayed.

Notes:

If you paste a valid credit card number manually in the credit card number field, the MM/YY field is displayed and by clicking in the MM/YY field the CC drop down is displayed and just after that the CC drop down could be opened also for the Credit Card Number. If the user select a card from the drop down the fields will be autofilled with the expiration date instead of the card number.
Please see the video attachment for a better understanding.

*The same issue is happening on target.com as well.

As a side note, the Security Code field is also treated as Password Field due to the type="password" attribute it has.

Suggesting S3 severity given the this is a more dynamic payment form and the behavior mentioned in Comment 1 is also password manager area which I will submit separately. This is also considered a P3 priority for autofill based on https://docs.google.com/spreadsheets/d/10V0bnw5nWM52ouADYM6H89B43v2JHKZaV1m3YZ8kiw0/edit#gid=0

Flags: needinfo?(gandalf)
Summary: CC Autofill does not work correctly on https://www.gap.com → [gap.com] CC Autofill does not work correctly
Whiteboard: [ccautofill] → [cc-autofill-reserve]

This is site specific. I verified that it also behaves the same way in Chromium.

Flags: needinfo?(gandalf)
Severity: -- → S4
Priority: -- → P3

I evaluated the reason behind it and it seems that we need more than one field to recognize a section as CC (or it has to be cc-number with autocomplete) as per [0] .

Chromium also doesn't recognize it as a CC form, likely for the same reason.

[0] https://searchfox.org/mozilla-central/rev/8df04ff073d0fa70f692935c5dcddc0e23cb0117/browser/extensions/formautofill/FormAutofillHandler.jsm#995-998

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: