And start demanding the member organizations to make a public statement as to exactly how far the EME DRM standardization is allowed to advance before they will withdraw from the W3C.
I am not sure of the official position, but I seriously doubt Mozilla will EVER implement this. They've been opposing H.264, which is a lesser evil (patents) than outright DRM.
They stopped opposing H.264 once they needed it for Firefox OS. I'd expect Mozilla to support the W3C DRM stuff as soon as someone makes Netflix a requirement for their Firefox OS phone. Maybe it won't be Mozilla but someone shipping Firefox OS will do the work. Then Mozilla will feel pressure to take the patch they provide. They're in a difficult position now that they're in the mobile phone OS market.
Or the very real possibility that Netflix (etc.) won't even be on the Firefox OS platform without EME.
Since Firefox OS builds on an Android userland there could be overlap in the hardware-mediated playback of protected content with Android devices based on the same SOC.
To be clear, after reading the EME spec it's primary a vehicle for transmitting the state of third-party module to Javascript, that module being permitted access to the media element backing a video or audio tag and to perform the final rendering of the content to an output device.
Those who are saying this spec precludes open implementations of a user agent (web browser) should probably read the spec. Some CDM vendors will restrict their plugin from working on open browsers, but there is no reason to do that as the CDM can be the unit processing the protected stream and rendering it. This means that open browsers can implement this spec and use CDMs that conform to an open ABI without compromising the protection of the content.
The CDM if used this way will be responsible for rendering a video or audio stream, not a shared graphics context like Flash or Java, and overlay graphics and UI will be implemented in standard HTML not in the closed CDM module.
It's about time to for the anti-DRM pressure groups to go down this list:
http://www.w3.org/Consortium/Member/List
And start demanding the member organizations to make a public statement as to exactly how far the EME DRM standardization is allowed to advance before they will withdraw from the W3C.