did this thread go anywhere ?<div>i'm concerned about the "maybe" case - looks way too much like:</div><div><a href="http://en.wikipedia.org/wiki/DShow#Codec_hell">http://en.wikipedia.org/wiki/DShow#Codec_hell</a><br>
<br></div><div>also - when you probe for mime type, do you mean the entire "type" parameter (including the codecs string) ? for example, there are too many cases where just passing "video/mp4" would be insufficient. (fragmented index support ? base/main/high profile ? paff ? cabac ?)</div>
<div><span class="Apple-style-span" style="color: rgb(34, 34, 34); font-family: -webkit-sans-serif; font-size: 16px; line-height: 21px; "><pre style="margin-left: 2em; white-space: pre-wrap; font-size: inherit; font-family: monospace; font-variant: normal; ">
<source src="video.mp4" type="video/mp4; codecs=&quot;avc1.42E01E, mp4a.40.2&quot;"></pre></span></div><div><br><div class="gmail_quote">On Wed, Oct 15, 2008 at 11:14 PM, Maciej Stachowiak <span dir="ltr"><<a href="mailto:mjs@apple.com">mjs@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d"><br>
On Oct 15, 2008, at 1:44 AM, Ian Hickson wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On Tue, 14 Oct 2008, Robert O'Callahan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Oct 14, 2008 at 12:13 PM, Maciej Stachowiak <<a href="mailto:mjs@apple.com" target="_blank">mjs@apple.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
While the underlying media frameworks can't necessarily answer, "if I<br>
give you a file with this MIME type, can you play it?", they can at<br>
least give a yes/no/maybe answer, which can still be quite helpful,<br>
since the UA will know it does not need to check some media streams at<br>
all.<br>
</blockquote>
<br>
I agree. If the API lets us answer "maybe", there is not much need or<br>
temptation to lie, and we can still return information that could be<br>
useful to scripts.<br>
</blockquote>
<br>
I have added window.navigator.canPlayType(mimeType). It returns 1, 0, or<br>
-1 to represent positive, neutral, and negative responses.<br>
</blockquote>
<br></div>
This API would be tempting to treat as a boolean but would of course do completely the wrong thing. I think it would be better to either ensure that the positive and neutral responses are both values that JS would treat as true (for instance make the values true, "maybe" and false), or else make all of the return values something self-descriptive and symbolic (for instance the strings "yes", "maybe" and "no"). I think 1, 0, -1 are neither clear nor likely to be in any way beneficial for perforamnce.<br>
<br>
Regards,<br><font color="#888888">
Maciej<br>
<br>
</font></blockquote></div><br></div>