- From: <bugzilla@jessica.w3.org>
- Date: Mon, 08 Sep 2014 23:03:04 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26738 --- Comment #9 from David Dorwin <ddorwin@google.com> --- The combination in comment #8 highlights another issue - the Stream Format and Initialization Data Format Registry unnecessarily binds container parsing with Initialization Data formats. In reality: * The "cenc" Initialization Data Type can be present in multiple containers. * The "keyids" Initialization Data Type is container-independent and has no stream format sections. * The "webm" Initialization Data Type is still only used by WebM but is not specific to WebM. It could just as easily be "keyid". Now that the Initialization Data format is no longer determined based on the container type, we should consider separating the container details from the Initialization Data types/formats. The container details could refer to the Initialization Data Type that they use. Note that this means that simply checking whether the initDataType is supported is no longer sufficient to determine whether the user agent can play a stream - it only indicates whether the CDM can generate a request based on that type. Specifically, any instances of isTypeSupported("com.example.somesystem", "cenc") need to be replaced with isTypeSupported("com.example.somesystem", "cenc", "video/mp4") This was already the case for "keyids", and providing the container and codecs should be a best practice anyway. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 8 September 2014 23:03:05 UTC