Short URL: http://html5.org/r/2427
| SVN | Bug | Comment | Time (UTC) |
|---|---|---|---|
| 2427 | NPAPI implementations apparently include the attributes of the <object> in what they send to the plugin. | 2008-11-22 00:53 |
Index: source =================================================================== --- source (revision 2426) +++ source (revision 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