W3C home > Mailing lists > Public > public-html-diffs@w3.org > June 2009

Be clearer that Content-Type headers are honoured for <video>. (whatwg r3231)

From: poot <cvsmail@w3.org>
Date: Sat, 13 Jun 2009 03:55:31 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090612185531.99D162BC2B@toro.w3.mag.keio.ac.jp>
Be clearer that Content-Type headers are honoured for <video>. (whatwg
r3231)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2379&r2=1.2380&f=h
http://html5.org/tools/web-apps-tracker?from=3230&to=3231

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2379
retrieving revision 1.2380
diff -u -d -r1.2379 -r1.2380
--- Overview.html	12 Jun 2009 18:44:54 -0000	1.2379
+++ Overview.html	12 Jun 2009 18:55:17 -0000	1.2380
@@ -18514,9 +18514,15 @@
      to network errors, causing the user agent to give up trying to
      fetch the resource</dt>
 
-     <dt>If the <a href="#media-data">media data</a> can be fetched but is in an
-     unsupported format, or can otherwise not be rendered at
-     all</dt>
+     <dt>If the <a href="#media-resource">media resource</a> is found to have <a href="#content-type-0" title="Content-Type">Content-Type metadata</a> that, when
+     parsed as a MIME type (including any codecs described by the
+     <code title="">codec</code> parameter), 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>
 
      <dd>
Received on Friday, 12 June 2009 18:56:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:08:57 UTC