The issue here is that the expiry date field is in an <iframe> that is disconnected from the cc-number field. [For a credit card section to be valid for autofill/autocomplete, it must contain a "cc-number" field and one of the following: autocomplete="on" attribute, cc-exp field, cc-name field.](https://searchfox.org/mozilla-central/rev/df6434d2ebfdf2b5f89f205fc81d60d64a774fe1/toolkit/components/formautofill/FormAutofillHandler.jsm#1047-1051). Since the expiry date is disconnected from the cc-number field, we will never show the autocomplete dropdown. This is probably a case of a hidden form that has two-way data binding on the visible form. In other words, if **we the browser** autofill the credit card number, the **we the browser** probably autofill into some hidden fields that then are copied into the visible fields via **website** logic.
Bug 1740665 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The issue here is that the expiry date field is in an <iframe> that is disconnected from the cc-number field. [For a credit card section to be valid for autofill/autocomplete, it must contain a "cc-number" field and one of the following: autocomplete="on" attribute, cc-exp field, cc-name field](https://searchfox.org/mozilla-central/rev/df6434d2ebfdf2b5f89f205fc81d60d64a774fe1/toolkit/components/formautofill/FormAutofillHandler.jsm#1047-1051). Since the expiry date is disconnected from the cc-number field, we will never show the autocomplete dropdown. This is probably a case of a hidden form that has two-way data binding on the visible form. In other words, if **we the browser** autofill the credit card number, the **we the browser** probably autofill into some hidden fields that then are copied into the visible fields via **website** logic.