I think Google has been first in implementing the proposed EME standard in HTML5 video. The ARM Chromebooks have been already using it to see Netflix video since a few months. Netflix can use Silverlight in IE11, but ARM Chromebooks don't have an alternative way of support and don't forget that Youtube doesn't like people easily downloading their videos like they do now.
And I think Chrome nightlies had the web DRM in place but were not enabled by default? Don't quote me on that.
Anyway, I think Firefox will be forced follow Chrome and IE now to implement DRM in HTML5 video. Firefox does not have the market power it once had thanks to Chrome.
Remember how the whole H.264 in HTML5 support thing played out for Firefox? They were on the side of not supporting it, and Google said it would remove it from Chrome, but that never happened, and Mozilla finally got tired of the effects of "Firefox doesn't support this site's video, let me use a browser that does" and added support.
The same thing is pretty much guaranteed to happen with EME as sites start using EME to stream video and IE, Chrome and Safari add support.
http://hothardware.com/News/Netflix-Backing-HTML5-But-Not-Wi...
And I think Chrome nightlies had the web DRM in place but were not enabled by default? Don't quote me on that.
Anyway, I think Firefox will be forced follow Chrome and IE now to implement DRM in HTML5 video. Firefox does not have the market power it once had thanks to Chrome.
Remember how the whole H.264 in HTML5 support thing played out for Firefox? They were on the side of not supporting it, and Google said it would remove it from Chrome, but that never happened, and Mozilla finally got tired of the effects of "Firefox doesn't support this site's video, let me use a browser that does" and added support.
The same thing is pretty much guaranteed to happen with EME as sites start using EME to stream video and IE, Chrome and Safari add support.