EME Web DRM

Umm noEME Standardized the Plugin err "extension" API. It in no way standardizes DRM. The Stardardization is around the way Javascript will be used to call inside HTML5 the browsers CDM (content decryption module" which is a plugin by another name.There are currently 3 competing technologies, with more to come, that are incompatible with FOSS, incompatible with open systemsFor Chrome Browsers there is Google Widevine CDMFor MS Browsers there is MS PlayReadyFor Fi

Wouldn't the sites just not allow the content to play on a non-DRM approved browser?

The DRM isn't actually implemented by the browser its more of a plugin architecture (Encrypted Media Extensions) which commercial closed source DRM plugin can fill.

Could be some DRM tech that will become mandatory to view the web

Doesn't Firefox block DRM content by default? If they continue to do so, and if Chrome does so, then this shouldn't have much effect. If most peoples browsers block it, apps shouldn't use it.

If you're referring to Encrypted Media Extensions it's not a DRM mechanism that requires proprietary software. It's a specification for a communication channel between a browser and Digital Rights Management agent software on the local machine. While it's not ideal, it's just some javascript functions that interact with the DRM on the computer. The DRM software itself is completely optional.It's much better than having plugins that do the same thing (if you use f

DRM isn't in html specs. This is just a standardized interface to a vendor-supplied DRM component.

Sure, the user may want to access DRM-encumbered content, but we shouldn't promote such a thing. You're not denying the users anything by refusing to implement EME, the media companies are denying the users freedom by insisting on using malware to deliver content! Just because users want Netflix in Firefox doesn't mean that it's the right thing to provide.

DRM is only there because of Chrome implementing it, Firefox resisted but had to give up due to market share.

Unfortunately, since the W3C caved on EME and DRMs apis for videos (i.e. plugins), there is a possibility of seeing that scheme being extended to images or text content. They caved once, there is absolutely no guarantee they wont cave again in the future and put the interests of a few companies before the idea of a free web.