False alarm: Chrome considers the number field to be a credit card field

I have a form with no credit card fields . However, in one of the fields with the number Chrome says that autocompletion of a credit card is disabled because this form does not use a secure connection:

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

The application will use HTTPS in production, but in any case this is a false signal.

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

  • step="1"
  • autocomplete="off"
  • x-autocompletetype="other"
+4
source share

Source: https://habr.com/ru/post/1662151/


All Articles