spec checked
MDN autocomplete name tokens
Documents autocomplete name for a person's full name, says using name is generally preferred because of diverse human-name structures, and lists component tokens including honorific-prefix, given-name, additional-name, family-name, honorific-suffix, and nickname when a service needs separate fields.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Name entry | Choose name entry when the product must capture a person's name for identification, correspondence, display, official records, booking, payment, verification, support, or relationship handling. | Users can type, paste, autofill, edit, select, undo, and correct names through native text behavior. | MDN supports autocomplete name and split-name component tokens only when those parts are deliberately collected. |
Evidence Role
This source is treated as spec evidence. Use it to validate the decision rules above, not as a visual style reference.
Publisher: MDN Web Docs. Last checked: .