Re:Requirements for DRM in HTML are confidential
by makomk on Tuesday January 14, 2014 @09:17AM
(#7057132)
Currently CDM decryptors are bundled with the browser, which in turn is generally locked to a particular OS or device. Browser vendors don't have to provide a way to install different decryptors and many of them aren't planning to.
Also, the actual user experience is not going to be a pure HTML5 player. Since this is intended to support hardware DRM that overlays the video onto the rendered page itself, sites have to assume the video is basically a rectangle crudely inserted into the page just like with plugins. They might be able to overlay stuff like controls on the top using HTML, but it's not clear if they'll even be able to rely on that.
Re:Requirements for DRM in HTML are confidential
by hsivonen on Wednesday January 15, 2014 @02:23AM
(#7062090)
None of the ones that have shipped already are installed like browser plug-ins. The ones Netflix deploys (PlayReady on Windows 8.1 with IE11 and Widevine on Chrome OS with Chrome) are bundled with operating systems and work with the browsers (one per OS) bundled with those operating systems.
Either way, the actual user experience is going to be a pure HTML5 player. If I have to install something first, that's unfortunate, but once it's installed I'll never have to think about it again, unlike the current situation where I'm confronted with the crappy plugin-based user experience every time I use the site.