2 ms·
In fact, this isn't killing NPAPI and replacing it with a smaller API, it's killing it and replacing it with no API at all: there is no longer a public API betw
by makomk 13y ago
In fact, this isn't killing NPAPI and replacing it with a smaller API, it's killing it and replacing it with no API at all: there is no longer a public API between the browser and the proprietary DRM blobs, and in some implementations (e.g. Microsoft's) there's no seperation between the two at all.
Not only that, but in practice HTML5 EME is designed to allow the "proprietary surface" of the web to be extended right down to the kernel and hardware itself. Take a look at the existing Chromebook implementation of HTML5 EME used by Netflix for example: it's tied to approved Chromebooks which are locked down at the hardware level to ensure no unauthorised programs are running anywhere on the machine. Enable developer mode to run your own software and the EME module disables itself. The spec even has restrictions on how videos can be embedded in webpages to support hardware-level DRM.
Now, technically EME implementations don't have to be any more restrictive than existing solutions like Flash, but since they can be companies like Netflix are going to be pressured by content providers into only supporting implementations that are "secure" and give their "high-value" content the protection it deserves. Which means hardware-level lockdowns and restrictions on video outputs (the HTML5 EME spec already has an error code for playback being blocked because the video connector doesn't support DRM).