1844026 - [ES][hsnstore.com] The CC dropdown is not displayed and the autofill is not working for the CC Number field

Status: VERIFIED FIXED

(Toolkit :: Form Autofill, task, P3)

Description

[Alin Ilea, Desktop Test Engineering]

Attachment: 2023-07-06_14h47_29.mp4

Found in

• 117.0a1

Affected versions

• 117.0a1

Tested platforms

• Affected platforms: Windows 10, macOS 12, Ubuntu 20

Preconditions

• browser.search.region to ES
• extensions.formautofill.creditCards.supportedCountries to ES
• have an already CC saved in about:preferences

Steps to reproduce

1. Reach the payment form on https://www.hsnstore.com
2. Click on the CC Number field in order to trigger de CC dropdown

Expected result

• The autofill dropdown should be displayed and choosing a CC entry should autofill all the eligible CC fields.

Actual result

• The CC dropdown is not displayed and the autofill is not working for the CC Number field.

Regression range

• N/A

Additional notes

• Not reproducible in Chrome.
• CC Number field has the autocomplete = "off" attribute.
• Fathom Fox Sample

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

:ailea, if you think that's a regression, could you try to find a regression range using for example mozregression?

Comment 2

[Hani Yacoub, Desktop QA]

Attachment: Screenshot 2024-09-09 at 14.48.50.png

I've retested this on the latest Nightly 132.0a1 on macOS 14.

• Autofill can't be triggered from "CC name" field
• Autofill can be triggered from "CC number" but only autofilling that field

When the extensions.formautofill.heuristics.autofillSameOriginWithTop setting is set to true the only thing that is changing is triggering autofill from "CC number" is autofilling "Ex date" field.

Comment 3

[Hani Yacoub, Desktop QA]

Attachment: Screen Recording 2024-09-09 at 14.48.07.mov

Comment 4

[Alin Ilea, Desktop Test Engineering]

Fixed by bug 1916606. The CC Name and expiry date fields that is located in the main frame, are now autofilled and cleared accordingly.
As we agreed with the engineering team and based on this comment, I will mark this as fixed and verified.