[giow] (2) Allow <object> plugins to register for extensions, like <e…

…mbed>. git-svn-id: http://svn.whatwg.org/webapps@3830 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Sep 14, 2009 · 891b898 · 891b898
1 parent 1a52a40
commit 891b898
Show file tree

Hide file tree

Showing 2 changed files with 42 additions and 2 deletions.
diff --git a/index b/index
@@ -20160,6 +20160,7 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>
     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>
 
@@ -20474,7 +20475,25 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>
         "<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>
 

diff --git a/source b/source
@@ -21607,6 +21607,7 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
     title="">.swf</code>".</p>
 
     <!-- it's sad that we have to do extension sniffing. sigh. -->
+    <!-- see also <object> which has a similar step -->
 
    </li>
 
@@ -21950,7 +21951,27 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
         no <code title="attr-object-type">type</code> attribute on the
         <code>object</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 <span
+        title="url-path">&lt;path&gt;</span> component of the
+        <span>URL</span> of the specified resource (after any
+        redirects) matches a pattern that a <span>plugin</span>
+        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 <span title="url-path">&lt;path&gt;</span>
+        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>