W3C home > Mailing lists > Public > public-html-diffs@w3.org > November 2008

spec/Overview.html 1.1599 2427 NPAPI implementations apparently include

From: poot <cvsmail@w3.org>
Date: Sat, 22 Nov 2008 09:56:12 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20081122005613.1F58F2BC1B@toro.w3.mag.keio.ac.jp>

NPAPI implementations apparently include the attributes of the <object>
in what they send to the plugin. (whatwg r2427)

If the sandboxed plugins browsing context flag is set on the browsing context for which the object element's document is the active document, then the steps above must always act as if they had failed to find a plugin, even if one would otherwise have been used.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1599.html#sandboxPluginObject
name
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1599.html#attr-object-name
When the algorithm above instantiates a plugin, the user agent should pass the names and values of all the attributes on the element, and all the names and values of parameters given by param elements that are children of the object element, in tree order, to the plugin used. If the plugin supports a scriptable interface, the HTMLObjectElement object representing the element should expose that interface. The plugin is not a nested browsing context.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1599.html#object-plugin

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1598&r2=1.1599&f=h
http://html5.org/tools/web-apps-tracker?from=2426&to=2427

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1598
retrieving revision 1.1599
diff -u -d -r1.1598 -r1.1599
--- Overview.html	22 Nov 2008 00:20:46 -0000	1.1598
+++ Overview.html	22 Nov 2008 00:53:36 -0000	1.1599
@@ -13278,13 +13278,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 id=sandboxPluginObject>If the <a href=#sandboxed-plugins-browsing-context-flag>sandboxed plugins browsing
+  <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 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
   which the <code><a href=#the-object-element>object</a></code> element's document is the <a href=#active-document>active
   document</a>, then the steps above must always act as if they had
Received on Saturday, 22 November 2008 00:56:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:13:57 GMT