W3C home > Mailing lists > Public > public-html-diffs@w3.org > August 2010

hixie: canPlayType('application/octet-stream') should always return ''. (whatwg r5407)

From: poot <cvsmail@w3.org>
Date: Tue, 31 Aug 2010 11:06:31 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20100831020632.362952BC87@toro.w3.mag.keio.ac.jp>
hixie: canPlayType('application/octet-stream') should always return ''.
(whatwg r5407)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4316&r2=1.4317&f=h
http://html5.org/tools/web-apps-tracker?from=5406&to=5407

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4316
retrieving revision 1.4317
diff -u -d -r1.4316 -r1.4317
--- Overview.html	31 Aug 2010 00:35:36 -0000	1.4316
+++ Overview.html	31 Aug 2010 01:59:55 -0000	1.4317
@@ -20981,14 +20981,17 @@
   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 title="">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
+  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 title="">application/octet-stream</code>" when used <em>with</em>
-  parameters, e.g. "<code title="">application/octet-stream;codecs=theora</code>", <em>is</em>
+  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>.<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>
@@ -21003,14 +21006,14 @@
 
   <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>; it must return "<code title="">probably</code>" if the user agent is confident that the
+  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
   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. 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>" if the type
-  doesn't have a <code title="">codecs</code> parameter.</p>
+  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>" if the type doesn't have a <code title="">codecs</code> parameter.</p>
 
   </div><div class="example">
 
@@ -35048,8 +35051,8 @@
      there are no <a href="#concept-input-type-file-selected" title="concept-input-type-file-selected">selected files</a>,
      then append an entry in the <var title="">form data set</var>
      with the <var title="">name</var> as the name, the empty string
-     as the value, and <code title="">application/octet-stream</code>
-     as the type.</li>
+     as the value, and <code>application/octet-stream</code> as the
+     type.</li>
      <!-- https://bugzilla.mozilla.org/show_bug.cgi?id=529859 -->
 
      <li><p>Otherwise, if the <var title="">field</var> element is an
Received on Tuesday, 31 August 2010 02:00:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:50 UTC