W3C home > Mailing lists > Public > public-html-commits@w3.org > July 2008

html5/spec Overview.html,1.1116,1.1117

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 24 Jul 2008 02:28:58 +0000
To: public-html-commits@w3.org
Message-Id: <E1KLqZe-0002T3-Hp@lionel-hutz.w3.org>

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv9439

Modified Files:
	Overview.html 
Log Message:
make <embed> do extension sniffing, for compatibility with servers that send flash as text/plain, sigh. See Mozilla bug 347736. (credit: cb) (whatwg r1926)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1116
retrieving revision 1.1117
diff -u -d -r1.1116 -r1.1117
--- Overview.html	24 Jul 2008 02:02:15 -0000	1.1116
+++ Overview.html	24 Jul 2008 02:28:55 -0000	1.1117
@@ -16530,17 +16530,37 @@
    being embedded is defined as follows:
 
   <ol>
-   <li>If the element has a <code title=attr-embed-type><a
-    href="#type4">type</a></code> attribute, then the value of the <code
-    title=attr-embed-type><a href="#type4">type</a></code> attribute is the
-    <span>content's type</span>.
+   <li>
+    <p>If the element has a <code title=attr-embed-type><a
+     href="#type4">type</a></code> attribute, then the value of the <code
+     title=attr-embed-type><a href="#type4">type</a></code> attribute is the
+     <span>content's type</span>.
 
-   <li>Otherwise, if the specified resource has <a href="#content-type5"
-    title=Content-Type>explicit Content-Type metadata</a>, then that is the
-    <span>content's type</span>.
+   <li>
+    <p>Otherwise, if the <a href="#ltpathgt" title=url-path>&lt;path&gt;</a>
+     component of the <a href="#url">URL</a> of the specified resource <!--
+    XXX before or after redirects? -->
+     matches a pattern that a <a href="#plugin">plugin</a> supports, then the
+     <span>content's type</span> is the type that that plugin can handle.</p>
 
-   <li>Otherwise, the content has no type and there can be no appropriate <a
-    href="#plugin">plugin</a> for it.
+    <p class=example>For example, a plugin might say that it can handle
+     resources with <a href="#ltpathgt" title=url-path>&lt;path&gt;</a>
+     components that end with the four character string "<code
+     title="">.swf</code>".</p>
+
+    <p class=big-issue>It would be better if browsers didn't do extension
+     sniffing like this, and only based their decision on the actual contents
+     of the resource. Couldn't we just apply the <span>sniffed type of a
+     resource</span> steps?</p>
+
+   <li>
+    <p>Otherwise, if the specified resource has <a href="#content-type5"
+     title=Content-Type>explicit Content-Type metadata</a>, then that is the
+     <span>content's type</span>.
+
+   <li>
+    <p>Otherwise, the content has no type and there can be no appropriate <a
+     href="#plugin">plugin</a> for it.
   </ol>
 
   <p>Whether the resource is fetched successfully or not must be ignored when
Received on Thursday, 24 July 2008 02:29:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 October 2008 20:32:58 GMT