When a placeholder vanishes after typing, the field label has not necessarily disappeared. Separate the label, temporary hint and entered value. The native HTML example below shows why those three pieces of text should not be treated as interchangeable.
Label, hint, and entered value are different
Consider this hypothetical article-filter field. Its permanent label is Search topics, and its placeholder hint says e.g. footnotes. Before typing, the user can see both the label and the hint. After entering diagrams, the hint disappears because the field now has a value, while the label remains the field’s identifying text.
| Screen state | Label | Hint | Value |
|---|---|---|---|
| Empty | Search topics | e.g. footnotes | None |
| Typed | Search topics | Hidden | diagrams |
| Cleared | Search topics | e.g. footnotes | None |
This matches the documented purpose of a placeholder hint: it appears while an input has no value, is not a replacement for an associated label, and normally becomes invisible once text is present.
Worked interpretation of the example
Hypothetical observation: the user sees “Search topics,” types “diagrams,” and then sees only the typed word inside the control. Outcome: the visible hint has been replaced by the current input value; the label still identifies what the control is for. If the user clears the text, the hint may return. That visual return does not demonstrate that a server stored, deleted, or changed any record.
What this screen state cannot prove
A disappearing hint cannot establish whether a search was submitted, whether results were saved, or whether an account action occurred. Those questions require separate evidence outside this display change. If a control has only a hint and no persistent, understandable label, its purpose may become unclear after typing. A well-described field should remain identifiable even when its hint is hidden.