1821307 - [ES][kiabi.es] Autofill is not working at all for the card number field

Status: VERIFIED FIXED

(Toolkit :: Form Autofill, defect, P2)

Description

[Alin Ilea, Desktop Test Engineering]

Attachment: kiabi.es_autofill.mp4

Found in

• 111.0-candidates

Affected versions

• 111.0-candidates

Tested platforms

• Affected platforms: Windows 10

Preconditions

• browser.search.region to ES
• extensions.formautofill.creditCards.supportedCountries to ES

Steps to reproduce

1. Reach the payment form on https://www.kiabi.es
2. Click on the card number field.
3. Click on the expiry date field and select any saved entry from the CC drop-down.

Expected result

• The autofill dropdown should be displayed for each eligible CC field and choosing a CC entry from the expiry date field should autofill all the CC fields.

Actual result

• The autofill dropdown is not displayed for the card number field and it is also not autofilled after choosing a CC entry from another field.

Regression range

• N/A

Additional notes

• The card number field has the autocomplete = off attribute.
• In Chrome, only the selected field is previewed and autofilled. Clear form dropdown is not displayed at all there.
• Fathom Fox Sample

Comment 1

[Micah [:mtigley] (she/her)]

For the autofill dropdown to display on the CC-name field, we can add a new phrase to our ruleset: nombre.*tarjeta.

As for autofill not working when an entry is chosen, the input fields are isolated in their own iframes. This should be addressed in Bug 1815399

Comment 2

[Dimi Lee [:dimi]]

hi alin, could you help test this bug again with the latest nightly build? Thank you!

Comment 3

[Alin Ilea, Desktop Test Engineering]

Attachment: 2023-07-07_13h34_36.mp4

Verified the issue in the latest Nightly 117.0a1 (2023-07-06). Now, the CC dropdown is displayed and the autofill is working for the CC Number field, but the CC dropdown and the autofill are no longer working for the expiry date field.

Comment 4

[Micah [:mtigley] (she/her)]

CC autofill not working for the expiry date field may have been regressed by Bug 1836458. It appears that our autofill heuristics is identifying this as a "cc-exp-month" field. Dimi, it's possible there might be regexp that's causing the cc-exp field to match. Perhaps we'll need to make that regexp less strict as well?

Comment 5

[Micah [:mtigley] (she/her)]

(In reply to Micah [:mtigley] (she/her) from comment #4)

CC autofill not working for the expiry date field may have been regressed by Bug 1836458.

After discussing with Dimi, it turns out this isn't a regression. We recently implemented heuristics in Bug 1833618 where we only consider fields that are visible.

This is related to the expiry date field no longer showing here because the CC number field is isolated in its own iframe and so our heuristics cannot detect whether or not its visible on the form. Therefore, when the expiry date field is parsed, the field scanner only knows about the expiry date field and has nothing else to compare it to.

This means the "regression" observed in this bug is something that will be addressed when support is added for CC fields contained within an iframe. We can mark this issue as fixed since the dropdown is now working for CC number field, but should also make sure we track the issue we discovered here.

Alin would you be able to file a follow-up bug for this and have it block Bug 1815399? Thank you!

Comment 6

[Alin Ilea, Desktop Test Engineering]

Sure, here is the new bug for the expiry date field.