W3C home > Mailing lists > Public > public-html-media@w3.org > July 2016

[encrypted-media] "Get Supported Capabilities for Audio/Video Type" algorithm should treat null contentType the same as invalid contentType

From: Chris Pearce via GitHub <sysbot+gh@w3.org>
Date: Mon, 04 Jul 2016 03:25:19 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-163596982-1467602717-sysbot+gh@w3.org>
cpearce has just created a new issue for 
https://github.com/w3c/encrypted-media:

== "Get Supported Capabilities for Audio/Video Type" algorithm should 
treat null contentType the same as invalid contentType ==
The "Get Supported Capabilities for Audio/Video Type" algorithm has 
these steps:

> 3. If content type is the empty string, return null.
> 4. If content type is an invalid or unrecognized MIME type, continue
 to the next iteration.

An empty content type string is invalid. Why isn't it treated the same
 as other invalid or unrecognized MIME types, where we'd skip that 
content type and continue the next iteration? Why is an empty content 
type worse than other forms of invalid MIME types?

I propose we merge these two steps into:

> 3. If content type is the empty string, or is an invalid or 
unrecognized MIME type, continue to the next iteration.




Please view or discuss this issue at 
https://github.com/w3c/encrypted-media/issues/261 using your GitHub 
account
Received on Monday, 4 July 2016 03:25:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 4 July 2016 03:25:29 UTC