1401164 - [Form Autofill] Name on Card does not trigger credit card autofill and expiry date is auto-filled wrong on groupon.com

Status: NEW

(Web Compatibility :: Desktop, defect, P3)

Description

[Gabi Cheta [:Gabi] Release Desktop QA]

Attachment: grouponautofill.png

[Note]:
- Have at least one credit card profile saved under Preferences

[Affected versions]:
- 57.0a1 latest

[Affected platforms]:
- Windows 10 x64, Ubuntu 16.04 and MacOS 10.12.6

[Steps to reproduce]:
1. Launch Fx and go to groupon.com
2. Login with a valid account
3. Click to buy a deal
4. Proceed to the checkout page
5. Double click on Name on card field
6. Double click on Card number field 
7. Select credit card profile from autofill options
8. Observe the expiry date

[Expected result]:
- Name on card and credit number fields should trigger autofill option

[Actual result]:
- Name on Card field does not trigger autofill option
- Expiry date is autofilled in year/month format which trows "This card is expired" error

[Regression range]:
-Not Regression

[Additional notes]:
-

Comment 1

[Sean Lee [:seanlee][:weilonge]]

After investigating groupon.com, this issue is related to cc-name and cc-exp
1. cc-name - In their HTML, the card name field is `<input autocomplete="billing name">`, so autofilling feature recognized it as the name of the address profile rather than credit card one. It looks like a web-compat issue.

2. cc-exp - Based on the spec of cc-exp[1], the value of cc-exp field is defined as "Valid month string" e.g. 2014-12. I did not see any pattern related attribute (e.g. placeholder, pattern) in the input for us to predict the format.

[1] https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#attr-fe-autocomplete-cc-exp
[2] https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#valid-month-string

Comment 2

[Luke Chang [:lchang] (inactive)]

FWIW, Chrome fills "mm/yyyy" into "cc-exp" fields by default. Though I think we should follow the spec especially when the website uses @autocomplete explicitly and doesn't give any clue to the expected format.

Comment 3

[Luke Chang [:lchang] (inactive)]

According to comment 1, this bug could be fixed from website itself.

Comment 4

[Oana Arbuzov [:oanaarbuzov]]

@Gabi, is this still reproducible?

Comment 5

[Gabi Cheta [:Gabi] Release Desktop QA]

Issue is reproducible with the latest Nightly 62.0a1.

Comment 6

[Firefox Bug Husbandry Bot]

See bug 1547409. Moving webcompat whiteboard tags to keywords.