W3C home > Mailing lists > Public > public-html-diffs@w3.org > March 2011

hixie: revert r5836 per http://lists.w3.org/Archives/Public/public-html/2011Mar/0002.html (whatwg r5921)

From: poot <cvsmail@w3.org>
Date: Mon, 28 Feb 2011 19:20:02 -0500
To: public-html-diffs@w3.org
Message-Id: <E1PuDJq-0004qj-FC@jay.w3.org>
hixie: revert r5836 per http://lists.w3.org/Archives/Public/public-
html/2011Mar/0002.html (whatwg r5921)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4761&r2=1.4762&f=h
http://html5.org/tools/web-apps-tracker?from=5920&to=5921

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4761
retrieving revision 1.4762
diff -u -d -r1.4761 -r1.4762
--- Overview.html	28 Feb 2011 23:56:29 -0000	1.4761
+++ Overview.html	1 Mar 2011 00:18:50 -0000	1.4762
@@ -343,7 +343,7 @@
 
    <h1>HTML5</h1>
    <h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id="editor-s-draft-28-february-2011">Editor's Draft 28 February 2011</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-1-march-2011">Editor's Draft 1 March 2011</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -485,7 +485,7 @@
   Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation
   track.
-  This specification is the 28 February 2011 Editor's Draft.
+  This specification is the 1 March 2011 Editor's Draft.
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
   actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
   group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -22363,7 +22363,19 @@
   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.<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.<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>
 
    <dd>
 
@@ -22377,7 +22389,8 @@
 
   <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.
@@ -22924,6 +22937,13 @@
      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 Tuesday, 1 March 2011 00:20:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 1 March 2011 00:20:04 GMT