[html5] r4259 - [giow] (0) Clarify whether application/octet-stream with parameters is a type th [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2009-10-21 04:48:20 -0700 (Wed, 21 Oct 2009)
New Revision: 4259

Modified:
   complete.html
   index
   source
Log:
[giow] (0) Clarify whether application/octet-stream with parameters is a type that the user agent knows it cannot render
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7977

Modified: complete.html
===================================================================
--- complete.html	2009-10-21 11:38:04 UTC (rev 4258)
+++ complete.html	2009-10-21 11:48:20 UTC (rev 4259)
@@ -22384,13 +22384,18 @@
   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 title="">application/octet-stream</code>" is
+  <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
   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 title="">application/octet-stream</code>" when used <em>with</em>
+  parameters, e.g. "<code title="">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>.</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>

Modified: index
===================================================================
--- index	2009-10-21 11:38:04 UTC (rev 4258)
+++ index	2009-10-21 11:48:20 UTC (rev 4259)
@@ -22214,13 +22214,18 @@
   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 title="">application/octet-stream</code>" is
+  <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
   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 title="">application/octet-stream</code>" when used <em>with</em>
+  parameters, e.g. "<code title="">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>.</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>

Modified: source
===================================================================
--- source	2009-10-21 11:38:04 UTC (rev 4258)
+++ source	2009-10-21 11:48:20 UTC (rev 4259)
@@ -23875,13 +23875,21 @@
   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 title="">application/octet-stream</code>" is
+  <p>The <span>MIME type</span> "<code
+  title="">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
+  title="">application/octet-stream</code>" when used <em>with</em>
+  parameters, e.g. "<code
+  title="">application/octet-stream;codecs=theora</code>", <em>is</em>
+  <span>a type that the user agent knows it cannot render</span>.</p>
+
   <dl class="domintro">
 
    <dt><var title="">media</var> . <code title="dom-navigator-canPlayType">canPlayType</code>(<var title="">type</var>)</dt>