:user-valid and :user-invalid
The :user-invalid CSS pseudo-class represents any validated form element whose value isn't valid based on their validation constraints, after the user has interacted with it.
The :user-invalid pseudo-class must match an :invalid, :out-of-range, or blank-but :required element between the time the user has attempted to submit the form and before the user has interacted again with the form element.
Browser support
| Feature | Desktop | Mobile | ||||
|---|---|---|---|---|---|---|
| Chrome | Edge | Firefox | Safari | Chrome Android | Safari iOS | |
| 119 | 119 | 88 | 16.5 | 119 | 16.5 | |
| Other | ||||||
| `:user-valid` | 119 | 119 | 88 | 16.5 | 119 | 16.5 |
1+Supported (version) Not supported ※Has note Sub-feature descriptions sourced from MDN Web Docs (CC BY-SA 2.5)
Notes 1 item(s)
Implementation note
- Previously available under a different name: :-moz-ui-invalid (4)
Notes 1 item(s)
Implementation note
- Previously available under a different name: :-moz-ui-valid (4)
Syntax
CSS
input:user-valid {
border-color: #16a34a;
background-image: url('check.svg');
}
input:user-invalid {
border-color: #dc2626;
background-image: url('error.svg');
}
input:user-invalid + .error-message {
display: block;
}Live demo
Use cases
-
Browser-native behavior
Use :user-valid and :user-invalid to rely on the platform for behavior that would otherwise require extra code or CSS complexity.
-
Progressive enhancement
Enhance the experience where support exists while keeping a solid baseline elsewhere.
Cautions
- Check browser support and actual product need before adding a new platform feature widely.
- Keep feature usage understandable so future contributors know why it was chosen.
Accessibility
- New platform features should still preserve readable defaults and robust interaction patterns.
- Verify that enhancement paths do not leave unsupported environments with a broken experience.