Valid Autocomplete Tokens In JSX

Reports an autoComplete attribute on a JSX form control whose value is not a token of the HTML autofill vocabulary.

The autofill vocabulary is closed. A browser that does not recognise the value treats the field as on and guesses from the surrounding markup, which is the behaviour the author was trying to replace — so a misspelt token does not fail loudly, it silently restores the default. A password manager filling the wrong field, or an address form the browser refuses to complete, is usually this.

Every whitespace-separated token has to come from the vocabulary: the field names, the grouping modifiers (shipping, billing, the telephone kinds), the webauthn suffix, or a section- prefixed section name, whose remainder is author-chosen and therefore not checked. Only the controls that support autofill are judged — input, select and textarea.

Replace the value with the autofill token for the data the field collects, or write off to opt the field out. Where several groups of the same fields appear in one form, prefix each group with its own section- name so the browser keeps them apart.