Steps to reproduce
When querying EME using requestMediaKeySystemAccess, it ignores the
sessionTypes field. The field should specify what session types must be supported. This is useful to determine if persistent licenses are supported.
In the sample below, it queries using requestMediaKeySystemAccess and passes
persistent-license in the config. It returns successful, but fails to create a session with unsupported. The query should fail to indicate that the session type is not supported.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Ibrahim O.”
Changed Assigned To to “Venkat K.”
Changed Assigned To from “Venkat K.” to “Nishant N.”
Changed Assigned To from “Nishant N.” to “Shawn P.”
Changed Assigned To from “Shawn P.” to “Gurpreet V.”
Changed Status to “Not reproducible”
Still reproducible with Edge/16.16299.
@Gurpreet, can you be more specific when you set status to "not reproducible"? Not reproducible with which version of Edge? When can developers expect to see this fix?
Changed Status from “Not reproducible”
We can still reproduce in the latest stable.
I can also still reproduce with the technical preview, Edge 42.17127.1.0, EdgeHTML 17.17127.
- Microsoft Edge Team
Changed Status to “External”
This issue has been resolved External. This means this issue may require a new feature to be implemented or other work that is more significant than a typical bug. You may be able to find more information on this issue by searching for related features on status.microsoftedge.com and uservoice.microsoftedge.com.
What external product or feature does “external” refer to here?
Joey, interesting discussion about this topic at https://github.com/Dash-Industry-Forum/dash.js/issues/2658#issuecomment-405353828 where a Microsoft rep said that the key system is supposed to be actually “com.microsoft.playready.recommendation” to make the CDM return appropriate response for session type persistent-license.
And yes, judging by modifying your jsfiddle it does seem to work, see http://jsfiddle.net/46hq9j2u/3/ .
Microsoft must provide a reasonable documentation for this key system, if it is supposed to supersede, in their own words, legacy “com.microsoft.playready” key system for EME.
Once the purpose of this key system is clear, Shaka Player will likely need to incorporate this key system as well.
Thanks, Tomas. I’ll keep an eye on that issue in dash.js, and I look forward to official documentation from Microsoft.