html5/spec Overview.html,1.4686,1.4687

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv13955

Modified Files:
	Overview.html 
Log Message:
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. (whatwg r5836)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4686
retrieving revision 1.4687
diff -u -d -r1.4686 -r1.4687
--- Overview.html	5 Feb 2011 00:36:37 -0000	1.4686
+++ Overview.html	5 Feb 2011 01:32:01 -0000	1.4687
@@ -22224,19 +22224,7 @@
   it definitely <em>cannot</em> play media of that type.<p><dfn id="a-type-that-the-user-agent-knows-it-cannot-render">A type that the user agent knows it cannot render</dfn> is
   one that describes a resource that the user agent definitely does
   not support, for example because it doesn't recognize the container
-  type, or it doesn't support the listed codecs.<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 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.<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>
+  type, or it doesn't support the listed codecs.<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>
 
@@ -22250,8 +22238,7 @@
 
   <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.
@@ -22798,13 +22785,6 @@
      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>

Received on Saturday, 5 February 2011 01:32:08 UTC