[html5] r2427 - [] (0) NPAPI implementations apparently include the attributes of the <object> i [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2008-11-21 16:53:31 -0800 (Fri, 21 Nov 2008)
New Revision: 2427

Modified:
   index
   source
Log:
[] (0) NPAPI implementations apparently include the attributes of the <object> in what they send to the plugin.

Modified: index
===================================================================
--- index	2008-11-22 00:20:42 UTC (rev 2426)
+++ index	2008-11-22 00:53:31 UTC (rev 2427)
@@ -16223,13 +16223,16 @@
 
   </ol><p id=object-plugin>When the algorithm above instantiates a
   <a href=#plugin>plugin</a>, the user agent should pass the names and values
-  of all the <span title=concept-param-parameter>parameters</span>
+  of all the attributes on the element, and <!-- then a parameter
+  named "PARAM" whose value is null, and then --> all the names and
+  values of <span title=concept-param-parameter>parameters</span>
   given by <code><a href=#the-param-element>param</a></code> elements that are children of the
-  <code><a href=#the-object-element>object</a></code> element to the <a href=#plugin>plugin</a> used. If the
-  <a href=#plugin>plugin</a> supports a scriptable interface, the
-  <code><a href=#htmlobjectelement>HTMLObjectElement</a></code> object representing the element
-  should expose that interface. The <a href=#plugin>plugin</a> is not a
-  nested <a href=#browsing-context>browsing context</a>.</p>
+  <code><a href=#the-object-element>object</a></code> element, in <a href=#tree-order>tree order</a>, to the
+  <a href=#plugin>plugin</a> used. If the <a href=#plugin>plugin</a> supports a
+  scriptable interface, the <code><a href=#htmlobjectelement>HTMLObjectElement</a></code> object
+  representing the element should expose that interface. The
+  <a href=#plugin>plugin</a> is not a nested <a href=#browsing-context>browsing
+  context</a>.</p>
 
   <p id=sandboxPluginObject>If the <a href=#sandboxed-plugins-browsing-context-flag>sandboxed plugins browsing
   context flag</a> is set on the <a href=#browsing-context>browsing context</a> for

Modified: source
===================================================================
--- source	2008-11-22 00:20:42 UTC (rev 2426)
+++ source	2008-11-22 00:53:31 UTC (rev 2427)
@@ -17362,13 +17362,16 @@
 
   <p id="object-plugin">When the algorithm above instantiates a
   <span>plugin</span>, the user agent should pass the names and values
-  of all the <span title="concept-param-parameter">parameters</span>
+  of all the attributes on the element, and <!-- then a parameter
+  named "PARAM" whose value is null, and then --> all the names and
+  values of <span title="concept-param-parameter">parameters</span>
   given by <code>param</code> elements that are children of the
-  <code>object</code> element to the <span>plugin</span> used. If the
-  <span>plugin</span> supports a scriptable interface, the
-  <code>HTMLObjectElement</code> object representing the element
-  should expose that interface. The <span>plugin</span> is not a
-  nested <span>browsing context</span>.</p>
+  <code>object</code> element, in <span>tree order</span>, to the
+  <span>plugin</span> used. If the <span>plugin</span> supports a
+  scriptable interface, the <code>HTMLObjectElement</code> object
+  representing the element should expose that interface. The
+  <span>plugin</span> is not a nested <span>browsing
+  context</span>.</p>
 
   <p id="sandboxPluginObject">If the <span>sandboxed plugins browsing
   context flag</span> is set on the <span>browsing context</span> for