[Webkit-unassigned] [Bug 197433] Unprefixed EME with "com.apple.fps.1_0" fails with "The operation is not supported."

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=197433

--- Comment #2 from Jer Noble <jer.noble at apple.com> ---
(In reply to Joey Parrish from comment #0)
> Running the following in the Safari debugger on localhost (a secure origin)
> fails with "The operation is not supported":
> 
> minimalConfig = {videoCapabilities: [{contentType: 'video/mp4;
> codecs="avc1.42E01E"'}]};
> mk = await navigator.requestMediaKeySystemAccess('com.apple.fps.1_0',
> [minimalConfig]);

The "1_0" vs. "2_0" nomenclature in the prefixed API was necessary because of message passing protocol changes that were subsequently made unnecessary by the Modern EME API; namely, certificates get first-class treatment. Also, the "1_0" protocol only ever worked with HLS-backed video elements, due to the difference initialization data in HLS vs. ISO, something that was also given first class treatment in Modern EME.

> Has the key system ID changed?  Are there docs on this somewhere that I've
> missed?

Yes, you just need to use "com.apple.fps". We're still working on the Modern EME documentation; I apologize that it's not ready yet.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190501/a7d1079f/attachment-0001.html>