On the standards track: Yes
Is Experimental: No
Is Deprecated: No
In Chrome version 42 on 2015-04-14 Note: The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string. The function does not exist in insecure contexts. This was not enforced until Chrome 58.
In Chrome Android version 42 on 2015-04-15 Note: The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string. The function does not exist in insecure contexts. This was not enforced until Chrome Android 58.
In Edge version 13 on 2015-11-12
In Firefox version 38 on 2015-05-12 Note: Starting in Firefox 55, if neither audioCapabilities nor videoCapabilities is specified in supportedConfigurations, a warning is output to the web console. In addition, starting in Firefox 55, if in supportedConfigurations, either audioCapabilities's or videoCapabilities's contentType value doesn't specify a "codecs" substring to define allowed codecs within the media wrapper, a warning is output to the web console. See note below table for example and correction. In the future, if neither audioCapabilities nor videoCapabilities is specified in the supportedConfigurations, a NotSupported exception will be thrown.
In Firefox for Android version 38 on 2015-05-12 Note: Starting in Firefox for Android 55, if neither audioCapabilities nor videoCapabilities is specified in supportedConfigurations, a warning is output to the web console. In addition, starting in Firefox for Android 55, if in supportedConfigurations, either audioCapabilities's or videoCapabilities's contentType value doesn't specify a "codecs" substring to define allowed codecs within the media wrapper, a warning is output to the web console. See note below table for example and correction. In the future, if neither audioCapabilities nor videoCapabilities is specified in the supportedConfigurations, a NotSupported exception will be thrown.
Not in Internet Explorer
Not in Node.js
In Quest Browser version 5.0 on undefined Note: The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string. The function does not exist in insecure contexts. This was not enforced until Quest Browser 5.0.
In Opera version 29 on 2015-04-28 Note: The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string. The function does not exist in insecure contexts. This was not enforced until Opera 45.
In Opera Android version 29 on 2015-04-28 Note: The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string. The function does not exist in insecure contexts. This was not enforced until Opera 45.
In Safari version 12.1 on 2019-03-25
In Safari on iOS version 12.2 on 2019-03-25
In Samsung Internet version 4.0 on 2016-03-11 Note: The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string. The function does not exist in insecure contexts. This was not enforced until Samsung Internet 7.0.
In WebView Android version 43 on 2015-05-27 Note: The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string. The function does not exist in insecure contexts. This was not enforced until version 58.
In WebView on iOS version 12.2 on 2019-03-25