[html5] r3830 - [giow] (2) Allow <object> plugins to register for extensions, like <embed>.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-09-13 23:10:38 -0700 (Sun, 13 Sep 2009)
New Revision: 3830

Modified:
   index
   source
Log:
[giow] (2) Allow <object> plugins to register for extensions, like <embed>.

Modified: index
===================================================================
--- index	2009-09-14 05:34:12 UTC (rev 3829)
+++ index	2009-09-14 06:10:38 UTC (rev 3830)
@@ -20160,6 +20160,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>
 
@@ -20474,12 +20475,30 @@
         "<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><path></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><path></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>
+
+       <li>
+
         <p>If the <var title="">resource type</var> is still unknown,
         then change the <var title="">resource type</var> to instead
         be the <a href=#content-type-sniffing-0 title="content-type sniffing">sniffed type

Modified: source
===================================================================
--- source	2009-09-14 05:34:12 UTC (rev 3829)
+++ source	2009-09-14 06:10:38 UTC (rev 3830)
@@ -21607,6 +21607,7 @@
     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,12 +21951,32 @@
         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"><path></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"><path></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>
+
+       <li>
+
         <p>If the <var title="">resource type</var> is still unknown,
         then change the <var title="">resource type</var> to instead
         be the <span title="content-type sniffing">sniffed type