HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
583611984[Gecko] [Internet Explorer] [Opera] [Webkit] 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.2011-02-05 01:31
@@ -27675,57 +27675,40 @@ interface <dfn>HTMLAudioElement</dfn> : <span>HTMLMediaElement</span> {};</pre>
   bitrate (only the maximum bitrate). Thus, given a type, a user agent
   can often only know whether it <em>might</em> be able to play
   media of that type (with varying levels of confidence), or whether
   it definitely <em>cannot</em> play media of that type.</p>
 
   <p><dfn>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>
 
-  <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>
 
    <dd>
 
     <p>Returns the empty string (a negative response), "maybe", or
     "probably" based on how confident the user agent is that it can
     play media resources of the given type.</p>
 
    </dd>
 
   </dl>
 
   <div class="impl">
 
   <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;
   and it must return "<code title="">maybe</code>" otherwise.
   Implementors are encouraged to return "<code title="">maybe</code>"
   unless the type can be confidently established as being supported or
   not. Generally, a user agent should never return "<code
   title="">probably</code>" for a type that allows the <code
   title="">codecs</code> parameter if that parameter is not
   present.</p>
@@ -28403,28 +28386,20 @@ interface <dfn>HTMLAudioElement</dfn> : <span>HTMLMediaElement</span> {};</pre>
     title="concept-task">tasks</span> to process the data as it is
     being fetched must, when appropriate, include the relevant
     substeps from the following list:</p>
 
     <dl class="switch">
 
      <dt>If the <span>media data</span> cannot be fetched at all, due
      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>
 
      <dd>
 
       <p>DNS errors, HTTP 4xx and 5xx errors (and equivalents in
       other protocols), and other fatal network errors that occur
       before the user agent has established whether the <var
       title="">current media resource</var> is usable, as well as

|