[Bug 21016] Please split Clear Key into a separate optional specification

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21016

--- Comment #7 from Henri Sivonen <hsivonen@iki.fi> ---
My point is that Chromium doesn't get Clear Key "for free" thanks to their
existing MP4/H.264/AAC support without rearranging their code. They don't get
it as a side effect of integrating with Widevine, either.

Obviously, they are able to support Clear Key and *could* rearrange code to
avoid code copying, but what's the point of having to rearrange code in order
to support a debugging mechanism that none of the proponents of EME intend to
target "premium content" to?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 28 February 2013 15:05:33 UTC