Behavior comparison
Search field vs Text field
Decisive difference
Search field submits a query and often clears or suggests as you type; Text field edits a general value stored in a form.
Choice criteria, links and sources
- Search fieldChoose Search field if the entered text is a query against a site, catalog, or result set.Open entry Search field
- Text fieldChoose Text field if the value is a name, email, code, or another short entry kept as data.Open entry Text field
See the nine dimensionsSee the sources
Enter text
Try it
Is the expected value short, multiline, or a search query?
Search field
Shared trial context
A form collects text, with field length and submission intent determining the appropriate input control.
Search field
Mission
Search field
Search for dialog, submit the query, then open one of the displayed concept results.
Step 1 of 3
Try
Try the component. Your live result appears just above. Move on at your own pace.
Behavior and edge case
- What to observe
- The named search landmark contains the query field, visible submit action, and clear control when populated.
- Edge case
- A query with no match shows an explicit empty result, while the simulated failure preserves the input and offers Retry.
Text field
Mission
Text field
Enter a valid name, submit, then exceed the limit and recover from the linked validation message.
Step 1 of 3
Try
Try the component. Your live result appears just above. Move on at your own pace.
Behavior and edge case
- What to observe
- The visible label, current value, and helper text remain available before any error.
- Edge case
- After invalid submission, the entered text remains, the precise error is linked, and focus moves only according to the form recovery plan.
What this example shows
Search field submits a query; Text field edits a general value, while Textarea accepts multiline content.
Which fits your need?
Search field
Searching a site, catalog, or results collection
Text field
Entering a name, email, code, or other short value
Difference and sources
Search field submits a query; Text field edits a general value, while Textarea accepts multiline content.
Read the sourcesParts of the specimen
Select a numbered marker on the schematic, or use the list below, to see its role. The schematic shows the concept's representative state.
Label
The persistent text that names a control or field.
Decision
Family question
Is the expected value short, multiline, or a search query?
Three criteria to choose
- Use case
Search field
Searching a site, catalog, or results collection
Text field
Entering a name, email, code, or other short value
- Interactivity
Search field
Supports query entry, clear, submit, and result feedback; it is not an unlabeled generic text field.
Text field
Edits one line of text and exposes validation, required, disabled, and autocomplete behavior.
- Accessible role
Search field
search > input[type=search]
Text field
input[type=text]
Nine dimensions
- Trigger
Search field
Focus and type a query, then submit explicitly or meet documented live-search criteria.
Text field
Focus the labeled field, then type or paste a single-line value.
- Modality
Search field
Non-modal query input within a named search region.
Text field
Non-modal form input.
- Placement
Search field
In a header or search region directly connected to its results.
Text field
Inline in a form with a persistent label and nearby help or error text.
- Interactivity
Search field
Supports query entry, clear, submit, and result feedback; it is not an unlabeled generic text field.
Text field
Edits one line of text and exposes validation, required, disabled, and autocomplete behavior.
- Focus
Search field
Submitting leaves focus in the search form while results update below; clearing returns focus to the query field.
Text field
A visible focus indicator surrounds the field without hiding its value, label, or error.
- Dismissal
Search field
Not applicable: results update inline; Clear removes the query, submitted results, opened-result status, and errors.
Text field
Not applicable: the entered value remains until edited, reset, or intentionally submitted.
- Accessible role
Search field
search > input[type=search]
Text field
input[type=text]
- Use case
Search field
Searching a site, catalog, or results collection
Text field
Entering a name, email, code, or other short value
- Mobile behavior
Search field
Use the search keyboard and keep clear, submit, and results reachable while the keyboard is open.
Text field
Select the correct software keyboard and autocomplete purpose, and avoid text sizes that trigger viewport zoom.
| Dimension | Search fieldSearch field | Text fieldText field |
|---|---|---|
| Trigger | Focus and type a query, then submit explicitly or meet documented live-search criteria. | Focus the labeled field, then type or paste a single-line value. |
| Modality | Non-modal query input within a named search region. | Non-modal form input. |
| Placement | In a header or search region directly connected to its results. | Inline in a form with a persistent label and nearby help or error text. |
| Interactivity | Supports query entry, clear, submit, and result feedback; it is not an unlabeled generic text field. | Edits one line of text and exposes validation, required, disabled, and autocomplete behavior. |
| Focus | Submitting leaves focus in the search form while results update below; clearing returns focus to the query field. | A visible focus indicator surrounds the field without hiding its value, label, or error. |
| Dismissal | Not applicable: results update inline; Clear removes the query, submitted results, opened-result status, and errors. | Not applicable: the entered value remains until edited, reset, or intentionally submitted. |
| Accessible role | search > input[type=search] | input[type=text] |
| Use case | Searching a site, catalog, or results collection | Entering a name, email, code, or other short value |
| Mobile behavior | Use the search keyboard and keep clear, submit, and results reachable while the keyboard is open. | Select the correct software keyboard and autocomplete purpose, and avoid text sizes that trigger viewport zoom. |