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

hixie: (WIP - MIMESNIFF has not yet been updated accordingly) Change the spec to use MIMESNIFF rules for text tracks instead of blindly honouring MIME types. (whatwg r6721)

From: poot <cvsmail@w3.org>
Date: Thu, 20 Oct 2011 19:31:12 -0400
To: public-html-diffs@w3.org
Message-Id: <E1RH24t-0000LX-UK@jay.w3.org>
hixie: (WIP - MIMESNIFF has not yet been updated accordingly) Change the
spec to use MIMESNIFF rules for text tracks instead of blindly honouring
MIME types. (whatwg r6721)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5388&r2=1.5389&f=h
http://html5.org/tools/web-apps-tracker?from=6720&to=6721

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5388
retrieving revision 1.5389
diff -u -d -r1.5388 -r1.5389
--- Overview.html	20 Oct 2011 23:14:56 -0000	1.5388
+++ Overview.html	20 Oct 2011 23:30:57 -0000	1.5389
@@ -26299,26 +26299,22 @@
     <p>The <a href="#concept-task" title="concept-task">tasks</a> <a href="#queue-a-task" title="queue
     a task">queued</a> by the <a href="#fetch" title="fetch">fetching
     algorithm</a> on the <a href="#networking-task-source">networking task source</a> to
-    process the data as it is being fetched must examine the
-    resource's <a href="#content-type" title="Content-Type">Content Type
-    metadata</a>, once it is available, if it ever is. If no <a href="#content-type" title="Content-Type">Content Type metadata</a> is ever
-    available, or if the type is not recognised as a text track
-    format, then the resource's format must be assumed to be
-    unsupported (this causes the load to fail, as described below). If
-    a type is obtained, and represents a supported text track format,
-    then the resource's data must be passed to the appropriate parser
-    as it is received, with the <a href="#text-track-list-of-cues">text
-    track list of cues</a> being used for that parser's output.</p>
+    process the data as it is being fetched must <a href="#content-type-sniffing-0" title="Content-Type sniffing">determine the sniffed type of a the
+    resource</a>. If the sniffed type of the resource is not a
+    supported text track format, the load will fail, as described
+    below. Otherwise, the resource's data must be passed to the
+    appropriate parser
+    as it is received, with the <a href="#text-track-list-of-cues">text track list of cues</a>
+    being used for that parser's output.</p>
 
     <p>If the <a href="#fetch" title="fetch">fetching algorithm</a> fails for
     any reason (network error, the server returns an error code, a
     cross-origin check fails, etc), if <var title="">URL</var> is the
-    empty string, or if the fetched resource is not in a supported
-    format, then <a href="#queue-a-task">queue a task</a> to first change the
-    <a href="#text-track-readiness-state">text track readiness state</a> to <a href="#text-track-failed-to-load" title="text track
-    failed to load">failed to load</a> and then <a href="#fire-a-simple-event">fire a simple
-    event</a> named <code title="event-error">error</code> at the
-    <code><a href="#the-track-element">track</a></code> element; and then, once that <a href="#concept-task" title="concept-task">task</a> is <a href="#queue-a-task" title="queue a
+    empty string, or if the sniffed type of the resource is not a
+    supported text track format, then <a href="#queue-a-task">queue a task</a> to
+    first change the <a href="#text-track-readiness-state">text track readiness state</a> to <a href="#text-track-failed-to-load" title="text track failed to load">failed to load</a> and then
+    <a href="#fire-a-simple-event">fire a simple event</a> named <code title="event-error">error</code> at the <code><a href="#the-track-element">track</a></code>
+    element; and then, once that <a href="#concept-task" title="concept-task">task</a> is <a href="#queue-a-task" title="queue a
     task">queued</a>, move on to the step below labeled
     <i>monitoring</i>.</p>
Received on Thursday, 20 October 2011 23:31:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 October 2011 23:31:15 GMT