Open Bug 1740463 Opened 3 years ago Updated 2 years ago

[DE][zalando.de] The Cardholder Name and Expiration Date is not captured in the doorhanger nor stored in CC storage

Categories

(Toolkit :: Form Autofill, defect, P3)

Desktop
All
defect

Tracking

()

Tracking Status
firefox94 --- disabled
firefox95 --- disabled
firefox96 --- disabled

People

(Reporter: tbabos, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Attached image Doorhanger

Affected Versions:
All latest Firefox versions: Nightly 96.0a1, Beta 95, Release 94

Tested on:
MacOS 10.15

Preconditions:

  • browser.search.region DE
  • extensions.formautofill.supportedCountries DE
  • download latest Firefox Nightly with region locale (switch extensions.formautofill.available to "on" for testing non-Nightly builds)

Steps to reproduce:

  1. Reach the payment form on zalando.de
  2. Fill in all the requested fields on the CC form and submit
  3. Choose to save the CC info
  4. Check the saved CC in the Credit Card storage (about:preferences#privacy)

Expected Results:

  1. The Credit Card save doorhanger should be displayed and capture all the expected fields: Cardholder Name, CC number (****last 4 digits)
  2. The credit card should be saved and stored with all the expected info: card number, cardholder name, expiration date, card type

Actual Results:

  1. Only the credit card number was captured and displayed in the doorhanger.
  2. Only the credit card number was saved in the newly saved CC entry from storage

Notes:
Reproducible on Chrome: N/A - chrome doesn't display the doorhanger at all
Regression-range: not a regressions, broken since Bug 1688576 where it was first reported

Attached image CC storage

Reproduced the same issue on lidl.de and obi.de as well, using Windows 10 and latest Nightly 96.0a1.

See Also: → 1688576
Priority: -- → P2

This issue is most likely due to a hidden duplicate field on the site. Referring to my previous comment on Bug 1688576:

The previously mentioned hidden 1px autocomplete fields are probably also causing the issue regarding credit card capture. My current guess is that the 1px autocomplete fields are what we're using to capture the card details...and since I'm not actually interacting with those fields (and those fields are not in the same location as the visible card number field), we default to the section that has a credit card number which has no relation to the other card detail sections on the page...and that guess is sort of correct. When we go to create the credit card record after submitting the form we end up looping twice, once for the hidden 1px autocomplete fields, but we seem to return an empty records set on that loop, and the second time we grab the visible credit card number field. Since this visible field has no related fields, we don't capture the name and expiration date of the entered fields.

This might be tangentially related to Bug 1739709 since the hidden fields can't easily be interacted with by a user. Not making a see also relationship yet since they might not be related.

Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: