Skip to content
Permalink
Browse files

[] (0) First woefully inadequate cut at <applet>. Please file bugs if…

… you know better...

git-svn-id: http://svn.whatwg.org/webapps@4057 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
Hixie committed Sep 29, 2009
1 parent 45bb143 commit 229be4f6883663d22fb1d8a79831f804a8a44a3e
Showing with 33 additions and 8 deletions.
  1. +16 −4 index
  2. +17 −4 source
20 index
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>
21 source
its <span>fallback content</span>, 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
<span>plugin</span>, 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 <span
title="concept-param-parameter">parameters</span> given by
<code>param</code> elements that are children of the
<code>applet</code> element, in <span>tree order</span>, to the
<span>plugin</span> used. If the <span>plugin</span> supports a
scriptable interface, the <code>HTMLAppletElement</code> object
representing the element should expose that interface. The
<code>applet</code> element <span>represents</span> the
<span>plugin</span>.</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>applet</code> element must implement the
<code>HTMLAppletElement</code> interface.</p>

0 comments on commit 229be4f

Please sign in to comment.
You can’t perform that action at this time.