2 ms·
> What in the W3C EME standard cannot be freely implemented? As far as I know, EME is just a communications standard between the browser and components that are
by gsnedders 10y ago
> What in the W3C EME standard cannot be freely implemented? As far as I know, EME is just a communications standard between the browser and components that are not part of the browser to allow those components to provide media data for the browser to display.
That, sadly, isn't the case. (It would be much better if it were!) All the existing EME modules are embedded as part of the browser, and there definitely isn't any standardised API to communicate with a module external to the browser.
All EME defines is an API on HTMLMediaElement to communicate with this abstract module, which yes, would allow the case of hiding the key from third parties to be addressed.
- hsivonen 10y ago> All the existing EME modules are embedded as part of the browser The CDMs used by Firefox, Chrome and Opera on Windows and Mac are distinct downloadables although the browsers handle the download automatically. The CDMs used by Chrome for Android, Edge and Safari are bundled with the underlying platform and aren't embedded in the browser (though these browsers are bundled with their platform).