On 5/18/14, 12:51 AM, Jim wrote:
It does require that the JS component communicating with the CDM via the EME is a standard. Netflix might refuse to support this standard, but you could try.
We've tried to get that part standardized, and failed.
If you are sandboxing the CDM, and if the CDM only verifies that it is running in this sandbox, then it should make no difference if it is part of a web browser or part of a dedicated media player, so it could be re-purposed for use in such a media player.
That's correct, as long as you use the same sandbox.
This would allow the DRM media player to be kept out of the web.
This seems like a pretty arbitrary distinction: using a browser plug-in vs launching a helper app that does the same thing. The end result is still DRM media on the web relying on the user having the DRM-enabled player.
The web browser and DRM player are separate.
Why is this particular bit important? I genuinely don't understand why having web browser and an always-present DRM player is any different than just having the web browser include the player.
No DRM extensions would be added to web standards.
That's happening no matter what we do... -Boris _______________________________________________ governance mailing list governance@lists.mozilla.org https://lists.mozilla.org/listinfo/governance
