autocomplete Attribute PickerBuild a valid autocomplete value for any form field. Pick a WHATWG autofill token, optionally add a section-* prefix so browsers keep the tokens for two different addresses separate, add scope keywords (shipping / billing for addresses, home / work / mobile / fax / pager for phones), tack on webauthn for conditional-UI passkeys, and copy a ready-to-paste <input> with the right type, inputmode, enterkeyhint, and maxlength. The linter flags common footguns like autocomplete="off" on password inputs (browsers ignore it) or a token that only applies to a different <input type>.
type, name, and label text as autofill signals too — a tel-national autocomplete on a text field labelled “phone” still fills, but type="tel" also brings the numeric keypad on mobile.Click any token to load it into the picker.
autocomplete="off" is a hint that browsers ignore for type="password", credit-card fields, and most modern password managers — use new-password / current-password instead so managers can tell “set a new one” from “fill the current one.”one-time-code triggers iOS & Android SMS autofill when combined with inputmode="numeric". Chrome on Android also honours the @domain #code convention in the SMS body.section-* prefix keeps two logical sections apart — e.g. section-billing given-name + section-shipping given-name tells the browser these are different people, so it won’t fill both from one profile.webauthn is appended (space-separated) to signal conditional-UI passkey autofill: autocomplete="username webauthn".street-address) and a multi-line form (address-line1..3) — pick one or the other, not both.cc-exp-month and cc-exp-year should be paired only when the user picks month/year separately. If you have one field for both, use cc-exp and accept MM/YY or MM/YYYY.autocomplete="shipping street-address", not autocomplete="street-address shipping".