:in-range

Read More at MDN DocsView Spec

Safe to Use

:in-range is considered safe to use.

It’s supported by 94% of global browsers.

Browsers

ChromeMar 8, 2011v10.0.0
26%╱100%
100% of Chrome users are running a supported version.
SafariJul 20, 2011v5.1.0
5%╱100%
100% of Safari users are running a supported version.
EdgeNov 12, 2015v13.0.0
5%╱100%
100% of Edge users are running a supported version.
FirefoxApr 29, 2014v29.0.0
3%╱100%
100% of Firefox users are running a supported version.

Version Breakdown

 
Agent
Support
Adoption
Chrome
Mar 8, 2011 v10.0.0
26%╱100%
100% of Chrome users are running a supported version.
Mar 8, 2011 – Latest
v10.0.0+
26%╱100%

Full Support

Before 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.

Chrome Android
Jun 27, 2012 v18.0.0
36%╱100%
100% of Chrome Android users are running a supported version.
Jun 27, 2012 – Latest
v18.0.0+
36%╱100%

Full Support

Before 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.

Edge
Nov 12, 2015 v13.0.0
5%╱100%
100% of Edge users are running a supported version.
Nov 12, 2015 – Latest
v13.0.0+
5%╱100%

Full Support

Firefox
Apr 29, 2014 v29.0.0
3%╱100%
100% of Firefox users are running a supported version.
Apr 29, 2014 – Latest
v29.0.0+
3%╱100%

Full Support

Before 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.

Firefox for Android
Oct 9, 2012 v16.0.0
Firefox for Android supports this feature.
Oct 9, 2012 – Latest
v16.0.0+

Full Support

Internet Explorer
Unsupported
Internet Explorer does not support this feature.

No Support

 
Quest Browser
Unknown v5.0.0
Quest Browser supports this feature.
Unknown
v5.0.0+

Full Support

Before 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.

Opera
Dec 16, 2010 v11.0.0
1%╱100%
100% of Opera users are running a supported version.
Dec 16, 2010 – Latest
v11.0.0+
1%╱100%

Full Support

Before 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.

Opera Android
Mar 22, 2011 v11.0.0
Opera Android supports this feature.
Mar 22, 2011 – Latest
v11.0.0+

Full Support

Before 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.

Safari
Jul 20, 2011 v5.1.0
5%╱100%
100% of Safari users are running a supported version.
Jul 20, 2011 – Latest
v5.1.0+
5%╱100%

Full Support

In Safari, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.

Safari on iOS
Oct 12, 2011 v5.0.0
17%╱100%
There are no users of Safari on iOS running a supported version.
Oct 12, 2011 – Latest
v5.0.0+
17%╱100%

Full Support

In Safari, :in-range matched disabled and read-only inputs (see bug 156530). It was later changed to only match enabled read-write inputs.

Samsung Internet
Apr 27, 2013 v1.0.0
2%╱100%
100% of Samsung Internet users are running a supported version.
Apr 27, 2013 – Latest
v1.0.0+
2%╱100%

Full Support

Before 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.

WebView Android
May 20, 2010 v2.2.0
WebView Android supports this feature.
May 20, 2010 – Latest
v2.2.0+

Full Support

Before 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.

See Also

Contribute