[html5] r3498 - [e] (0) Ignore application/octet-stream when used to label videos. Add a note to [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2009-07-30 15:43:01 -0700 (Thu, 30 Jul 2009)
New Revision: 3498

Modified:
   index
   source
Log:
[e] (0) Ignore application/octet-stream when used to label videos. Add a note to the WebSocket security section.

Modified: index
===================================================================
--- index	2009-07-29 23:38:21 UTC (rev 3497)
+++ index	2009-07-30 22:43:01 UTC (rev 3498)
@@ -71,7 +71,7 @@
   <div class=head>
    <p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
    <h1>HTML 5</h1>
-   <h2 class="no-num no-toc" id=draft-standard-—-date:-01-jan-1901>Draft Standard — 29 July 2009</h2>
+   <h2 class="no-num no-toc" id=draft-standard-—-date:-01-jan-1901>Draft Standard — 30 July 2009</h2>
    <p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -20509,6 +20509,13 @@
   not support, for example because it doesn't recognize the container
   type, or it doesn't support the listed codecs.</p>
 
+  <p>The MIME type "<code title="">application/octet-stream</code>" 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>
+
   <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-07-29 23:38:21 UTC (rev 3497)
+++ source	2009-07-30 22:43:01 UTC (rev 3498)
@@ -22000,6 +22000,13 @@
   not support, for example because it doesn't recognize the container
   type, or it doesn't support the listed codecs.</p>
 
+  <p>The MIME type "<code title="">application/octet-stream</code>" 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>
+
   <dl class="domintro">
 
    <dt><var title="">media</var> . <code title="dom-navigator-canPlayType">canPlayType</code>(<var title="">type</var>)</dt>
@@ -71073,9 +71080,13 @@
   <p class="XXX">...</p>
 
   <!-- should mention that servers should only echo the origin if they
-  want to talk to that origin -->
+  want to talk to any origin -->
 
+  <!-- should mention that clients and server can just bail if they
+  run out of resources (or hit an artificial resource limit intended
+  to avoid resource starvation) trying to read a frame -->
 
+
   <h5>IANA considerations</h5>
 
   <p class="XXX">...(two URI schemes, two ports, HTTP Upgrade keyword)</p>