requestMediaKeySystemAccess
|
Chrome
Full support
42
Full support
42
Notes' The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string.
Notes' The function does not exist in insecure contexts. This was not enforced until Chrome 58.
|
Edge
Full support
13
|
Firefox
Full support
38
Full support
38
Notes' Starting in Firefox 55, if neither audioCapabilities nor videoCapabilities is specified in supportedConfigurations, a warning is output to the web console.
Notes' 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.
Notes' In the future, if neither audioCapabilities nor videoCapabilities is specified in the supportedConfigurations, a NotSupported exception will be thrown.
|
IE
No support
No
|
Opera
Full support
29
Full support
29
Notes' The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string.
Notes' The function does not exist in insecure contexts. This was not enforced until Opera 45.
|
Safari
Full support
13.1
|
WebView Android
Full support
43
Full support
43
Notes' The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string.
Notes' The function does not exist in insecure contexts. This was not enforced until version 58.
|
Chrome Android
Full support
42
Full support
42
Notes' The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string.
Notes' The function does not exist in insecure contexts. This was not enforced until Chrome 58.
|
Firefox Android
Full support
38
Full support
38
Notes' Starting in Firefox 55, if neither audioCapabilities nor videoCapabilities is specified in supportedConfigurations, a warning is output to the web console.
Notes' 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.
Notes' In the future, if neither audioCapabilities nor videoCapabilities is specified in the supportedConfigurations, a NotSupported exception will be thrown.
|
Opera Android
Full support
29
Full support
29
Notes' The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string.
Notes' The function does not exist in insecure contexts. This was not enforced until Opera 45.
|
Safari iOS
Full support
13.4
|
Samsung Internet Android
Full support
4.0
Full support
4.0
Notes' The spec requires that the passed supportedConfigurations option contain at least one of audioCapabilities or videoCapabilities, and that said parameters include a codec string.
Notes' The function does not exist in insecure contexts. This was not enforced until Samsung Internet 7.0.
|