ValidityState.typeMismatch
Draft: This page is not complete.
typeMismatch
property of a ValidityState
object indicates if the value of an <input>
, after having been edited by the user, does not conform to the constraints set by the element's type
attribute. If the type
attribute expects specific strings, such as the email and url types and the value don't doesn't conform to the constraints set by the type, the typeMismatch
property will be true.
The email input type expects one or more valid email addresses, depending on whether the multiple
attribute is present. A valid email address includes an email prefix and a domain, with or without a top level domain. If the value of the email input is not an empty string, a single valid e-mail address, or one or more comma separated email address if the multiple
attribute is present, there is a typeMismatch
.
The url input type expects one or more valid email URLs, depending on whether the multiple
attribute is present. A valid URL includes a protocol, optionally with an IP address, or an optional subdomain, domain, and top level domain combination. If the value of the URL input is not an empty string, a single valid URL, or one or more comma separated URLS if the multiple
attribute is present, there is a typeMismatch
.
Input type | Value | Expected value |
---|---|---|
x@y or [email protected]
| email address, with or without TLD | |
url |
x: or x://y.z
| protocol or full URL with protocol |
Examples
Given the following:
<p> <label> Enter an email address: <input type="email" value="example.com"/> </label> </p> <p> <label> Enter a URL: <input type="url" value="example.com"/> </label> </p>
input:invalid { border: red solid 3px; }
The above each produce a typeMismatch
because the email address is just a domain and the URL has no protocol
The typeMismatch
occurs when there is a disconnect between the value
expected via the type
attribute and the data that is actually present. The typeMismatch
is only one of the many possible errors and is only relevant for the email and url types. When the value provided doesn't match the expected value based on the type for other input types, you get different errors. For example, if the number input value is not a floating point number, the badInput
is true
. If the email is required
but is empty, the valueMissing
will be true
.
Specifications
Specification |
---|
HTML Standard (HTML) # dom-validitystate-typemismatch |
Browser compatibility
Desktop | Mobile | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | WebView Android | Chrome Android | Firefox for Android | Opera Android | Safari on IOS | Samsung Internet | |
typeMismatch |
15 |
12 |
4 |
10 |
12.1 |
5 |
≤37 |
18 |
4 |
12.1 |
5 |
1.0 |
See also
© 2005–2021 MDN contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/API/ValidityState/typeMismatch