Steps to reproduce
When querying EME using
navigator.requestMediaKeySystemAccess, it doesn’t accept any robustness level. If one of the
audioCapabilities contain a
robustness value, even if it is the empty string (the default), it will indicate that it is not supported.
If you run that, it will display a count of 0, which is not intended. This suggests that it cannot decrypt the content type. An empty robustness level indicates that any robustness level can be used. So when EME returns without that in the capabilities, it suggests that it is not supported.
Commenting out the line setting the robustness will return the correct result. It will display 1 supported content type of
video/mp4. When the robustness is set to the empty string, it should be treated the same as missing.
Comments and activity
- Microsoft Edge Team
Changed Status to “Fixed”
Thank you for the feedback on Edge and the repro. In testing this out on internal builds I show this as being fixed. The specific build being tested is 14339.1000. As a result of this, the item is being resolved as fixed.
All the best,
The MS Edge Team