4 ms·
The CDM API is called "EME" and it is a standard. That's why Widevine can be made to work with Firefox (https://github.com/i-rinat/gmp-widevine https://github.
by mynameislegion 10y ago
The CDM API is called "EME" and it is a standard. That's why Widevine can be made to work with Firefox (https://github.com/i-rinat/gmp-widevine https://github.com/i-rinat/gmp-widevine).
EDIT: Firefox now supports Widevine
> Beginning in version 47, Firefox desktop also supports the Google Widevine CDM.
https://support.mozilla.org/en-US/kb/enable-drm https://support.mozilla.org/en-US/kb/enable-drm
The issue with browser-specific CDMs at this time seems to be only because of varying completeness of EME implementations.
- wmf 10y agoThat shim exists because Chrome and Firefox have different CDM APIs. There isn't a common API.
- mynameislegion 10y agoThe common API is called "EME". Chrome and Firefox's API's are different because they're unfinished.
- vetinari 10y agoThat "EME" API is what is exposed to scripts (think DOM). Not how the browser and CDM communicates (think XPCOM).
- bzbarsky 10y ago"EME" is the API CDMs expose to scripts, with browser mediation. It's not the API CDMs expose to the browser, which is not standardized at all, sadly. > The issue with browser-specific CDMs at this time seems to be only because of varying completeness of EME implementations. No, it's basically baked into the standard, because the editors were fine with having CDMs be browser-specific.
- slrz 10y agoBullshit. EME specifies a Javascript API for use by websites. What Firefox uses to talk with a CDM is right there in the name of that Github repo: it's an interface called GMP and was created by Mozilla specifically for video/media-type browser plugins. It's not used by Chrome, Safari or any other non-Mozilla browser.