W3C home > Mailing lists > Public > public-html-commits@w3.org > April 2011

html5/spec Overview.html,1.4816,1.4817

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 12 Apr 2011 22:13:56 +0000
To: public-html-commits@w3.org
Message-Id: <E1Q9lqO-00065F-Js@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv23371

Modified Files:
	Overview.html 
Log Message:
apply wg decision (whatwg r5994)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4816
retrieving revision 1.4817
diff -u -d -r1.4816 -r1.4817
--- Overview.html	12 Apr 2011 21:58:48 -0000	1.4816
+++ Overview.html	12 Apr 2011 22:13:52 -0000	1.4817
@@ -22410,13 +22410,22 @@
   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>
+  resource</a>.<p class="note">
+  "<code>application/octet-stream</code>"
+  is special-cased here; if any parameter appears with it, it
+  should
+  
+  be treated just like any other <a href="#mime-type">MIME type</a>.
+
+  This is a deviation from the rule <!-- in RFC 2046, section 1,
+  paragraph 3 --> that unknown <a href="#mime-type">MIME type</a> parameters
+  should be ignored.
+
+  <!-- but not really a "willful violation" since it's not that the
+  types are not being ignored, just that before the type is handled as
+  a type, there's a special case for a particular set of strings -->
+
+  <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>
 
Received on Tuesday, 12 April 2011 22:13:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 12 April 2011 22:14:38 GMT