spec 1 linked patterns 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.
Read with a purpose
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
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. |
Comparisons supported by this source
- Name entry vs text input vs autocomplete vs select vs inline validation vs error summary
MDN supports autocomplete name for full names and component tokens only when a service deliberately captures parts.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: MDN Web Docs. Last checked: .