[giow] (1) Bring the spec more in line with what the browsers do for …

…video (largely, ignoring Content-Type). This will probably be tweaked further once Adam's draft has a section dedicated to sniffing media container formats.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=11984

git-svn-id: http://svn.whatwg.org/webapps@5836 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -25730,22 +25730,6 @@ <h5 id=mime-types><span class=secno>4.8.10.3 </span>MIME types</h5>
  not support, for example because it doesn't recognize the container
  type, or it doesn't support the listed codecs.</p>

  <p>The <a href=#mime-type>MIME type</a>
  "<code>application/octet-stream</code>" with no parameters is never
  <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot render</a>. User
  agents must treat that type as equivalent to the lack of any
  explicit <a href=#content-type title=Content-Type>Content-Type metadata</a>
  when it is used to label a potential <a href=#media-resource>media
  resource</a>.</p>

  <p class=note>In the absence of a <!-- pretty crazy -->
  specification to the contrary, the <a href=#mime-type>MIME type</a>
  "<code>application/octet-stream</code>" when used <em>with</em>
  parameters, e.g.
  "<code>application/octet-stream;codecs=theora</code>", <em>is</em>
  <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot render</a>,
  since that parameter is not defined for that type.</p>

  <dl class=domintro><dt><var title="">media</var> . <code title=dom-navigator-canPlayType><a href=#dom-navigator-canplaytype>canPlayType</a></code>(<var title="">type</var>)</dt>

   <dd>
@@ -25760,8 +25744,7 @@ <h5 id=mime-types><span class=secno>4.8.10.3 </span>MIME types</h5>

  <p>The <dfn id=dom-navigator-canplaytype title=dom-navigator-canPlayType><code>canPlayType(<var title="">type</var>)</code></dfn> method must return the empty
  string if <var title="">type</var> is <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user
  agent knows it cannot render</a> or is the type
  "<code>application/octet-stream</code>"; it must return "<code title="">probably</code>" if the user agent is confident that the
  agent knows it cannot render</a>; it must return "<code title="">probably</code>" if the user agent is confident that the
  type represents a <a href=#media-resource>media resource</a> that it can render if
  used in with this <code><a href=#audio>audio</a></code> or <code><a href=#video>video</a></code> element;
  and it must return "<code title="">maybe</code>" otherwise.
@@ -26326,13 +26309,6 @@ <h5 id=loading-the-media-resource><span class=secno>4.8.10.5 </span>Loading the
     to network errors, causing the user agent to give up trying to
     fetch the resource</dt>

     <dt>If the <a href=#media-resource>media resource</a> is found to have <a href=#content-type title=Content-Type>Content-Type metadata</a> that, when
     parsed as a <a href=#mime-type>MIME type</a> (including any codecs
     described by the <code title="">codecs</code> parameter, if the
     parameter is defined for that type), represents <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that
     the user agent knows it cannot render</a> (even if the actual
     <a href=#media-data>media data</a> is in a supported format)</dt>

     <dt>If the <a href=#media-data>media data</a> can be fetched but is found by
     inspection to be in an unsupported format, or can otherwise not
     be rendered at all</dt>

index

@@ -25712,22 +25712,6 @@ interface <dfn id=htmlaudioelement>HTMLAudioElement</dfn> : <a href=#htmlmediael
  not support, for example because it doesn't recognize the container
  type, or it doesn't support the listed codecs.</p>

  <p>The <a href=#mime-type>MIME type</a>
  "<code>application/octet-stream</code>" with no parameters is never
  <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot render</a>. User
  agents must treat that type as equivalent to the lack of any
  explicit <a href=#content-type title=Content-Type>Content-Type metadata</a>
  when it is used to label a potential <a href=#media-resource>media
  resource</a>.</p>

  <p class=note>In the absence of a <!-- pretty crazy -->
  specification to the contrary, the <a href=#mime-type>MIME type</a>
  "<code>application/octet-stream</code>" when used <em>with</em>
  parameters, e.g.
  "<code>application/octet-stream;codecs=theora</code>", <em>is</em>
  <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot render</a>,
  since that parameter is not defined for that type.</p>

  <dl class=domintro><dt><var title="">media</var> . <code title=dom-navigator-canPlayType><a href=#dom-navigator-canplaytype>canPlayType</a></code>(<var title="">type</var>)</dt>

   <dd>
@@ -25742,8 +25726,7 @@ interface <dfn id=htmlaudioelement>HTMLAudioElement</dfn> : <a href=#htmlmediael

  <p>The <dfn id=dom-navigator-canplaytype title=dom-navigator-canPlayType><code>canPlayType(<var title="">type</var>)</code></dfn> method must return the empty
  string if <var title="">type</var> is <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user
  agent knows it cannot render</a> or is the type
  "<code>application/octet-stream</code>"; it must return "<code title="">probably</code>" if the user agent is confident that the
  agent knows it cannot render</a>; it must return "<code title="">probably</code>" if the user agent is confident that the
  type represents a <a href=#media-resource>media resource</a> that it can render if
  used in with this <code><a href=#audio>audio</a></code> or <code><a href=#video>video</a></code> element;
  and it must return "<code title="">maybe</code>" otherwise.
@@ -26308,13 +26291,6 @@ interface <dfn id=htmlaudioelement>HTMLAudioElement</dfn> : <a href=#htmlmediael
     to network errors, causing the user agent to give up trying to
     fetch the resource</dt>

     <dt>If the <a href=#media-resource>media resource</a> is found to have <a href=#content-type title=Content-Type>Content-Type metadata</a> that, when
     parsed as a <a href=#mime-type>MIME type</a> (including any codecs
     described by the <code title="">codecs</code> parameter, if the
     parameter is defined for that type), represents <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that
     the user agent knows it cannot render</a> (even if the actual
     <a href=#media-data>media data</a> is in a supported format)</dt>

     <dt>If the <a href=#media-data>media data</a> can be fetched but is found by
     inspection to be in an unsupported format, or can otherwise not
     be rendered at all</dt>

source

@@ -27682,22 +27682,6 @@ interface <dfn>HTMLAudioElement</dfn> : <span>HTMLMediaElement</span> {};</pre>
  not support, for example because it doesn't recognize the container
  type, or it doesn't support the listed codecs.</p>

  <p>The <span>MIME type</span>
  "<code>application/octet-stream</code>" with no parameters is never
  <span>a type that the user agent knows it cannot render</span>. User
  agents must treat that type as equivalent to the lack of any
  explicit <span title="Content-Type">Content-Type metadata</span>
  when it is used to label a potential <span>media
  resource</span>.</p>

  <p class="note">In the absence of a <!-- pretty crazy -->
  specification to the contrary, the <span>MIME type</span>
  "<code>application/octet-stream</code>" when used <em>with</em>
  parameters, e.g.
  "<code>application/octet-stream;codecs=theora</code>", <em>is</em>
  <span>a type that the user agent knows it cannot render</span>,
  since that parameter is not defined for that type.</p>

  <dl class="domintro">

   <dt><var title="">media</var> . <code title="dom-navigator-canPlayType">canPlayType</code>(<var title="">type</var>)</dt>
@@ -27717,8 +27701,7 @@ interface <dfn>HTMLAudioElement</dfn> : <span>HTMLMediaElement</span> {};</pre>
  <p>The <dfn title="dom-navigator-canPlayType"><code>canPlayType(<var
  title="">type</var>)</code></dfn> method must return the empty
  string if <var title="">type</var> is <span>a type that the user
  agent knows it cannot render</span> or is the type
  "<code>application/octet-stream</code>"; it must return "<code
  agent knows it cannot render</span>; it must return "<code
  title="">probably</code>" if the user agent is confident that the
  type represents a <span>media resource</span> that it can render if
  used in with this <code>audio</code> or <code>video</code> element;
@@ -28410,14 +28393,6 @@ interface <dfn>HTMLAudioElement</dfn> : <span>HTMLMediaElement</span> {};</pre>
     to network errors, causing the user agent to give up trying to
     fetch the resource</dt>

     <dt>If the <span>media resource</span> is found to have <span
     title="Content-Type">Content-Type metadata</span> that, when
     parsed as a <span>MIME type</span> (including any codecs
     described by the <code title="">codecs</code> parameter, if the
     parameter is defined for that type), represents <span>a type that
     the user agent knows it cannot render</span> (even if the actual
     <span>media data</span> is in a supported format)</dt>

     <dt>If the <span>media data</span> can be fetched but is found by
     inspection to be in an unsupported format, or can otherwise not
     be rendered at all</dt>