- From: poot <cvsmail@w3.org>
- Date: Tue, 29 Sep 2009 20:46:27 +0900 (JST)
- To: public-html-diffs@w3.org
hixie: First woefully inadequate cut at <applet>. Please file bugs if you know better... (whatwg r4057) http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3218&r2=1.3219&f=h http://html5.org/tools/web-apps-tracker?from=4056&to=4057 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.3218 retrieving revision 1.3219 diff -u -d -r1.3218 -r1.3219 --- Overview.html 29 Sep 2009 11:32:25 -0000 1.3218 +++ Overview.html 29 Sep 2009 11:46:06 -0000 1.3219 @@ -67862,10 +67862,22 @@ its <a href="#fallback-content">fallback content</a>, the element must be ignored (it represents nothing).</p> - <p>Otherwise, <span class="XXX">define how the element works, if - supported</span>.</p> <!-- remember to delay the load event --> <!-- - remember to include ", from the element's <span>browsing context - scope origin</span> if it has one" when fetching --> + <p>Otherwise, the user agent instantiate a Java Language runtime + <a href="#plugin">plugin</a>, if one available. Then, the user agent should + pass the names and values 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 <a href="#concept-param-parameter" title="concept-param-parameter">parameters</a> given by + <code><a href="#the-param-element">param</a></code> elements that are children of the + <code><a href="#the-applet-element">applet</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="#htmlappletelement">HTMLAppletElement</a></code> object + representing the element should expose that interface. The + <code><a href="#the-applet-element">applet</a></code> element <a href="#represents">represents</a> the + <a href="#plugin">plugin</a>.</p> + + <!-- If we ever make this fetch anything manually, remember to delay + the load event, and to include ", from the element's <span>browsing + context scope origin</span> if it has one" when fetching --> <p>The <code><a href="#the-applet-element">applet</a></code> element must implement the <code><a href="#htmlappletelement">HTMLAppletElement</a></code> interface.</p>
Received on Tuesday, 29 September 2009 11:47:03 UTC