False alarm: Chrome believes number field is credit card field

Asked Nov 28 '16 at 14:34

Active Oct 17 '17 at 20:37

Viewed 220 times

I have a form with no credit card fields at all. Still, on one of the number fields, Chrome says Credit card autofill is disabled because this form does not use a secure connection:

<input type="number" value="0" name="category[priority]" id="category_priority">

The app will use HTTPS in production, but this is a false alarm anyway.

How can I tell Chrome that field is not a credit card field? Things I tried:

step="1"
autocomplete="off"
x-autocompletetype="other"

edited Oct 17 '17 at 20:37

asked Nov 28 '16 at 14:34

João Souza

4,032
3
25
38

3

There is no credit card input. It's just a number field. – João Souza Nov 28 '16 at 14:38
Can you share the full html? That fragment should not trigger the autofill mechanism and does not for me if run in isolation. – Alex K. Nov 29 '16 at 11:11

False alarm: Chrome believes number field is credit card field

0 Answers0