html5/spec Overview.html,1.2997,1.2998

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

Modified Files:
	Overview.html 
Log Message:
Allow <object> plugins to register for extensions, like <embed>. (whatwg r3830)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2997
retrieving revision 1.2998
diff -u -d -r1.2997 -r1.2998
--- Overview.html	14 Sep 2009 05:28:57 -0000	1.2997
+++ Overview.html	14 Sep 2009 06:05:23 -0000	1.2998
@@ -17572,6 +17572,7 @@
     components that end with the four character string "<code title="">.swf</code>".</p>
 
     <!-- it's sad that we have to do extension sniffing. sigh. -->
+    <!-- see also <object> which has a similar step -->
 
    </li>
 
@@ -17857,7 +17858,25 @@
         "<code title="">application/octet-stream</code>" but there is
         no <code title="attr-object-type"><a href="#attr-object-type">type</a></code> attribute on the
         <code><a href="#the-object-element">object</a></code> element, then change the <var title="">resource type</var> to be unknown, so that the
-        sniffing rules in the next step are invoked.</p>
+        sniffing rules in the following steps are invoked.</p>
+
+       </li>
+
+       <li>
+
+        <p>If the <var title="">resource type</var> is still unknown
+        at this point, but the <a href="#url-path" title="url-path">&lt;path&gt;</a> component of the
+        <a href="#url">URL</a> of the specified resource (after any
+        redirects) matches a pattern that a <a href="#plugin">plugin</a>
+        supports, then let <var title="">resource type</var> be the
+        type that that plugin can handle.</p>
+
+        <p class="example">For example, a plugin might say that it can
+        handle resources with <a href="#url-path" title="url-path">&lt;path&gt;</a>
+        components that end with the four character string "<code title="">.swf</code>".</p>
+
+        <!-- it's sad that we have to do extension sniffing. sigh. -->
+        <!-- see also <embed> which has a similar step -->
 
        </li>

Received on Monday, 14 September 2009 06:05:37 UTC