The :in-range
CSS pseudo-class represents an <input>
element whose current value is within the range limits specified by the min
and max
attributes.
The :in-range
CSS pseudo-class represents an <input>
element whose current value is within the range limits specified by the min
and max
attributes.
This pseudo-class is useful for giving the user a visual indication that a field's current value is within the permitted limits.
Note: This pseudo-class only applies to elements that have (and can take) a range limitation. In the absence of such a limitation, the element can neither be "in-range" nor "out-of-range."
:in-range { /* ... */ }
<form action="" id="form1"> <ul> Values between 1 and 10 are valid. <li> <input id="value1" name="value1" type="number" placeholder="1 to 10" min="1" max="10" value="12" required /> <label for="value1">Your value is </label> </li> </ul> </form>
li { list-style: none; margin-bottom: 1em; } input { border: 1px solid black; } input:in-range { background-color: rgba(0, 255, 0, 0.25); } input:out-of-range { background-color: rgba(255, 0, 0, 0.25); border: 2px solid red; } input:in-range + label::after { content: "okay."; } input:out-of-range + label::after { content: "out of range!"; }
Note: An empty <input>
does not count as out of range, and will not be selected using the :out-of-range
pseudo-class selector. The :blank
pseudo-class exists to select blank inputs, although at the time of writing this is experimental and not well-supported. You could also use the required
attribute and the :invalid
pseudo-class to provide more general logic and styling for making inputs mandatory (:invalid
will style blank and out-of-range inputs).
Desktop | Mobile | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | WebView Android | Chrome Android | Firefox for Android | Opera Android | Safari on IOS | Samsung Internet | |
:in-range |
10Before Chrome 52,:in-range matched disabled and read-only inputs (see Chromium bug 602568). In Chrome 52, it was changed to only match enabled read-write inputs. |
13 | 29Before Firefox 50,:in-range matched disabled and read-only inputs (see bug 1264157). In Firefox 50, it was changed to only match enabled read-write inputs. |
No | 11Before Opera 39,:in-range matched disabled and read-only inputs (see Chromium bug 602568). In Opera 39, it was changed to only match enabled read-write inputs. |
5.1In Safari,:in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs. |
2.2Before version 52,:in-range matched disabled and read-only inputs (see Chromium bug 602568). In version 52, it was changed to only match enabled read-write inputs. |
18Before Chrome 52,:in-range matched disabled and read-only inputs (see Chromium bug 602568). In Chrome 52, it was changed to only match enabled read-write inputs. |
16 | 11Before Opera 39,:in-range matched disabled and read-only inputs (see Chromium bug 602568). In Opera 39, it was changed to only match enabled read-write inputs. |
5In Safari,:in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs. |
1.0Before version 6.0,:in-range matched disabled and read-only inputs (see Chromium bug 602568). In version 6.0, it was changed to only match enabled read-write inputs. |
© 2005–2023 MDN contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/CSS/:in-range