[html5] r1647 - /
whatwg at whatwg.org
whatwg at whatwg.org
Tue May 20 18:34:16 PDT 2008
Author: ianh
Date: 2008-05-20 18:34:16 -0700 (Tue, 20 May 2008)
New Revision: 1647
Modified:
index
source
Log:
[e] (0) Abstract out the concept of third-party renderers into the term "plugin" and put all its related text in one place. Also, quadruple prose/example/note/warning combo! 20 points.
Modified: index
===================================================================
--- index 2008-05-21 00:56:52 UTC (rev 1646)
+++ index 2008-05-21 01:34:16 UTC (rev 1647)
@@ -2541,6 +2541,32 @@
title="">TEXT_NODE</code> (3) or <code title="">CDATA_SECTION_NODE</code>
(4). <a href="#refsDOM3CORE">[DOM3CORE]</a>
+ <p>The term <dfn id=plugin>plugin</dfn> is used to mean any content
+ handler, typically a third-party content handler, for Web content types
+ that are not supported by the user agent natively, or for content types
+ that do not expose a DOM, that supports rendering the content as part of
+ the user agent's interface.
+
+ <p class=example>One example of a plugin would be a PDF viewer that is
+ instantiated in a <a href="#browsing1">browsing context</a> when the user
+ navigates to a PDF file. This would count as a plugin regardless of
+ whether the party that implemented the PDF viewer component was the same
+ as that which implemented the user agent itself. However, a PDF viewer
+ application that launches separate from the user agent (as opposed to
+ using the same interface) is not a plugin by this definition.
+
+ <p class=note>This specification does not define a mechanism for
+ interacting with plugins, as it is expected to be user-agent- and
+ platform-specific. Some UAs might opt to support a plugin mechanism such
+ as the Netscape Plugin API; others might use remote content convertors or
+ have built-in support for certain types. <a href="#refsNPAPI">[NPAPI]</a>
+
+ <p class=warning>Browsers should take extreme care when interacting with
+ external content intended for <a href="#plugin" title=plugin>plugins</a>.
+ When third-party software is run with the same privileges as the user
+ agent itself, vulnerabilities in the third-party software become as
+ dangerous as those in the user agent.
+
<p>Some of the algorithms in this specification, for historical reasons,
require the user agent to <dfn id=pause>pause</dfn> until some condition
has been met. While a user agent is paused, it must ensure that no scripts
@@ -14277,11 +14303,11 @@
<dt>The <dfn id=sandboxed0>sandboxed plugins browsing context flag</dfn>
<dd>
- <p>This flag prevents content from instantiating third-party handlers
- (i.e. plugins), whether using <a href="#sandboxPluginEmbed">the
- <code>embed</code> element</a>, <a href="#sandboxPluginObject">the
- <code>object</code> element</a>, <a href="#sandboxPluginApplet">the
- <code>applet</code> element</a>, or <a
+ <p>This flag prevents content from instantiating <a href="#plugin"
+ title=plugin>plugins</a>, whether using <a
+ href="#sandboxPluginEmbed">the <code>embed</code> element</a>, <a
+ href="#sandboxPluginObject">the <code>object</code> element</a>, <a
+ href="#sandboxPluginApplet">the <code>applet</code> element</a>, or <a
href="#sandboxPluginNavigate">through navigation</a> of a <a
href="#nested0">nested browsing context</a>.</p>
@@ -14542,11 +14568,12 @@
context</a> for which the <code><a href="#embed">embed</a></code>
element's document is the <a href="#active">active document</a>, then the
user agent must render the <code><a href="#embed">embed</a></code> element
- in a manner that conveys that the plugin was disabled. The user agent may
- offer the user the option to override the sandbox and instantiate the
- handler anyway; if the user invokes such an option, the user agent must
- act as if the <a href="#sandboxed0">sandboxed plugins browsing context
- flag</a> was not set for the purposes of this element.
+ in a manner that conveys that the <a href="#plugin">plugin</a> was
+ disabled. The user agent may offer the user the option to override the
+ sandbox and instantiate the <a href="#plugin">plugin</a> anyway; if the
+ user invokes such an option, the user agent must act as if the <a
+ href="#sandboxed0">sandboxed plugins browsing context flag</a> was not set
+ for the purposes of this element.
<p class=warning>Plugins are disabled in sandboxed browsing contexts
because they might not honour the restrictions imposed by the sandbox
@@ -14559,32 +14586,26 @@
context:
<p>When the <code title=attr-embed-src><a href="#src3">src</a></code>
- attribute is set, user agents are expected to find an appropriate handler
- for the specified resource, based on the <a href="#type-of"
- title=concept-embed-type>content's type</a>, and hand that handler the
- content of the resource. If the handler supports a scriptable interface,
- the <code><a href="#htmlembedelement">HTMLEmbedElement</a></code> object
- representing the element should expose that interfaces.
+ attribute is set, user agents are expected to find an appropriate <a
+ href="#plugin">plugin</a> for the specified resource, based on the <a
+ href="#type-of" title=concept-embed-type>content's type</a>, and hand that
+ <a href="#plugin">plugin</a> the content of the resource. If the <a
+ href="#plugin">plugin</a> supports a scriptable interface, the <code><a
+ href="#htmlembedelement">HTMLEmbedElement</a></code> object representing
+ the element should expose that interfaces.
<p>The download of the resource must <a href="#delays">delay the <code
title=event-load>load</code> event</a>.
<p>The user agent should pass the names and values of all the attributes of
the <code><a href="#embed">embed</a></code> element that have no namespace
- to the handler used. Any (namespace-less) attribute may be specified on
- the <code><a href="#embed">embed</a></code> element.</p>
- <!-- duplicates what's in <object> section below -->
+ to the <a href="#plugin">plugin</a> used. Any (namespace-less) attribute
+ may be specified on the <code><a href="#embed">embed</a></code> element.
- <p class=note>This specification does not define a mechanism for
- interacting with third-party handlers, as it is expected to be
- user-agent-specific. Some UAs might opt to support a plugin mechanism such
- as the Netscape Plugin API; others may use remote content convertors or
- have built-in support for certain types. <a href="#refsNPAPI">[NPAPI]</a>
-
<p>The <code><a href="#embed">embed</a></code> element has no <a
href="#fallback">fallback content</a>. If the user agent can't display the
specified resource, e.g. because the given type is not supported, then the
- user agent must use a default handler for the content. (This default could
+ user agent must use a default plugin for the content. (This default could
be as simple as saying "Unsupported Format", of course.)
<p>The <dfn id=type4 title=attr-embed-type><code>type</code></dfn>
@@ -14605,8 +14626,8 @@
title=Content-Type>explicit Content-Type metadata</a>, then that is the
<span>content's type</span>.
- <li>Otherwise, the content has no type and there can be no appropriate
- handler for it.
+ <li>Otherwise, the content has no type and there can be no appropriate <a
+ href="#plugin">plugin</a> for it.
</ol>
<p class=big-issue>Should we instead say that the content-sniffing used for
@@ -14618,11 +14639,6 @@
<p class=big-issue>We should say that 404s, etc, don't affect whether the
resource is used or not. Not sure how to say it here though.
- <p>Browsers should take extreme care when interacting with external content
- intended for third-party renderers. When third-party software is run with
- the same privileges as the user agent itself, vulnerabilities in the
- third-party software become as dangerous as those in the user agent.
-
<p>The <code><a href="#embed">embed</a></code> element supports <a
href="#dimension0">dimension attributes</a>.
@@ -14691,8 +14707,8 @@
<p>The <code><a href="#object">object</a></code> element can represent an
external resource, which, depending on the type of the resource, will
either be treated as an image, as a nested <a href="#browsing1">browsing
- context</a>, or as an external resource to be processed by a third-party
- software package.
+ context</a>, or as an external resource to be processed by a <a
+ href="#plugin">plugin</a>.
<p>The <dfn id=data title=attr-object-data><code>data</code></dfn>
attribute, if present, specifies the address of the resource. If present,
@@ -14727,14 +14743,16 @@
<li>
<p>If the <code title=attr-object-classid>classid</code> attribute is
present, and has a value that isn't the empty string, then: if the user
- agent can find a handler suitable according to the value of the <code
- title=attr-object-classid>classid</code> attribute, and <a
- href="#sandboxPluginObject">handlers aren't being sandboxed</a>, then
- that handler <a href="#object-plugin">should be used</a>, and the value
- of the <code title=attr-object-data><a href="#data">data</a></code>
- attribute, if any, should be passed to the handler. If no suitable
- handler can be found, or if the handler reports an error, jump to the
- last step in the overall set of steps (fallback).</p>
+ agent can find a <a href="#plugin">plugin</a> suitable according to the
+ value of the <code title=attr-object-classid>classid</code> attribute,
+ and <a href="#sandboxPluginObject">handlers aren't being sandboxed</a>,
+ then that <a href="#plugin">plugin</a> <a href="#object-plugin">should
+ be used</a>, and the value of the <code title=attr-object-data><a
+ href="#data">data</a></code> attribute, if any, should be passed to the
+ <a href="#plugin">plugin</a>. If no suitable <a
+ href="#plugin">plugin</a> can be found, or if the <a
+ href="#plugin">plugin</a> reports an error, jump to the last step in the
+ overall set of steps (fallback).</p>
<!--
case insensitive:
is "clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" -> application/x-shockwave-flash
@@ -14755,10 +14773,10 @@
<li>
<p>If the <code title=attr-object-type><a href="#type6">type</a></code>
attribute is present and its value is not a type that the user agent
- supports, and is not a type that the user agent can find a handler
- for, then the user agent may jump to the last step in the overall set
- of steps (fallback) without downloading the content to examine its
- real type.
+ supports, and is not a type that the user agent can find a <a
+ href="#plugin">plugin</a> for, then the user agent may jump to the
+ last step in the overall set of steps (fallback) without downloading
+ the content to examine its real type.
<li>
<p>Begin a load for the resource.</p>
@@ -14818,15 +14836,16 @@
matches:</p>
<dl class=switch>
- <dt>If the <var title="">resource type</var> can be handled by a
- special handler (e.g. a plugin), and <a
- href="#sandboxPluginObject">handlers aren't being sandboxed</a>
+ <dt>If the <var title="">resource type</var> can be handled by a <a
+ href="#plugin">plugin</a> and <a href="#sandboxPluginObject">plugins
+ aren't being sandboxed</a>
<dd>
- <p>The user agent <a href="#object-plugin">should use that
- handler</a> and pass the content of the resource to that handler. If
- the handler reports an error, then jump to the last step in the
- overall set of steps (fallback).</p>
+ <p>The user agent <a href="#object-plugin">should use that plugin</a>
+ and pass the content of the resource to that <a
+ href="#plugin">plugin</a>. If the <a href="#plugin">plugin</a>
+ reports an error, then jump to the last step in the overall set of
+ steps (fallback).</p>
<dt>If the <var title="">resource type</var> is an <span>XML MIME
type</span><!-- XXX xref -->
@@ -14899,12 +14918,14 @@
<p>If the <code title=attr-object-data><a href="#data">data</a></code>
attribute is absent but the <code title=attr-object-type><a
href="#type6">type</a></code> attribute is present, <a
- href="#sandboxPluginObject">handlers aren't being sandboxed</a>, and the
- user agent can find a handler suitable according to the value of the
- <code title=attr-object-type><a href="#type6">type</a></code> attribute,
- then that handler <a href="#object-plugin">should be used</a>. If no
- suitable handler can be found, or if the handler reports an error, jump
- to the next step (fallback).
+ href="#sandboxPluginObject">plugins aren't being sandboxed</a>, and the
+ user agent can find a <a href="#plugin">plugin</a> suitable according to
+ the value of the <code title=attr-object-type><a
+ href="#type6">type</a></code> attribute, then that <a
+ href="#plugin">plugin</a> <a href="#object-plugin">should be used</a>.
+ If no suitable <a href="#plugin">plugin</a> can be found, or if the <a
+ href="#plugin">plugin</a> reports an error, jump to the next step
+ (fallback).
<li>
<p>(Fallback.) The <code><a href="#object">object</a></code> element
@@ -14913,32 +14934,24 @@
element's <a href="#fallback">fallback content</a>.
</ol>
- <p id=object-plugin>When the algorihm above instantiates a handler, the
- user agent should pass the names and values of all the <span
- title=concept-param-parameter>parameters</span> given by <code><a
- href="#param">param</a></code> elements that are children of the <code><a
- href="#object">object</a></code> element to the handler used. If the
- handler supports a scriptable interface, the <code><a
+ <p id=object-plugin>When the algorihm 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> given by
+ <code><a href="#param">param</a></code> elements that are children of the
+ <code><a href="#object">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 handler is not a nested <a
- href="#browsing1">browsing context</a>.
+ the element should expose that interface. The <a href="#plugin">plugin</a>
+ is not a nested <a href="#browsing1">browsing context</a>.
<p id=sandboxPluginObject>If the <a href="#sandboxed0">sandboxed plugins
browsing context flag</a> is set on the <a href="#browsing1">browsing
context</a> for which the <code><a href="#object">object</a></code>
element's document is the <a href="#active">active document</a>, then the
- steps above must always act as if they had failed to find a handler, even
- if one would otherwise have been used.</p>
- <!-- duplicates what's in <embed> section above -->
+ steps above must always act as if they had failed to find a <a
+ href="#plugin">plugin</a>, even if one would otherwise have been used.
- <p class=note>The <code><a href="#object">object</a></code> element can, in
- certain cases as described above, instantiate third-party handlers. This
- specification does not define a mechanism for interacting with third-party
- handlers, as it is expected to be user-agent-specific. Some UAs might opt
- to support a plugin mechanism such as the Netscape Plugin API; others may
- use remote content convertors or have built-in support for certain types.
- <a href="#refsNPAPI">[NPAPI]</a>
-
<p>Due to the algorithm above, the contents of <code><a
href="#object">object</a></code> elements act as <a
href="#fallback">fallback content</a>, used only when referenced resources
@@ -15037,8 +15050,7 @@
</dl>
<p>The <code><a href="#param">param</a></code> element defines parameters
- for handlers invoked by <code><a href="#object">object</a></code>
- elements.
+ for plugins invoked by <code><a href="#object">object</a></code> elements.
<p>The <dfn id=name5 title=attr-param-name><code>name</code></dfn>
attribute gives the name of the parameter.
Modified: source
===================================================================
--- source 2008-05-21 00:56:52 UTC (rev 1646)
+++ source 2008-05-21 01:34:16 UTC (rev 1647)
@@ -810,6 +810,35 @@
or <code title="">CDATA_SECTION_NODE</code> (4). <a
href="#refsDOM3CORE">[DOM3CORE]</a></p>
+ <p>The term <dfn>plugin</dfn> is used to mean any content handler,
+ typically a third-party content handler, for Web content types that
+ are not supported by the user agent natively, or for content types
+ that do not expose a DOM, that supports rendering the content as
+ part of the user agent's interface.</p>
+
+ <p class="example">One example of a plugin would be a PDF viewer
+ that is instantiated in a <span>browsing context</span> when the
+ user navigates to a PDF file. This would count as a plugin
+ regardless of whether the party that implemented the PDF viewer
+ component was the same as that which implemented the user agent
+ itself. However, a PDF viewer application that launches separate
+ from the user agent (as opposed to using the same interface) is not
+ a plugin by this definition.</p>
+
+ <p class="note">This specification does not define a mechanism for
+ interacting with plugins, as it is expected to be user-agent- and
+ platform-specific. Some UAs might opt to support a plugin mechanism
+ such as the Netscape Plugin API; others might use remote content
+ convertors or have built-in support for certain types. <a
+ href="#refsNPAPI">[NPAPI]</a></p>
+
+ <p class="warning">Browsers should take extreme care when
+ interacting with external content intended for <span
+ title="plugin">plugins</span>. When third-party software is run with
+ the same privileges as the user agent itself, vulnerabilities in the
+ third-party software become as dangerous as those in the user
+ agent.</p>
+
<p>Some of the algorithms in this specification, for historical
reasons, require the user agent to <dfn>pause</dfn> until some
condition has been met. While a user agent is paused, it must ensure
@@ -12294,8 +12323,8 @@
<dd>
- <p>This flag prevents content from instantiating third-party
- handlers (i.e. plugins), whether using <a
+ <p>This flag prevents content from instantiating <span
+ title="plugin">plugins</span>, whether using <a
href="#sandboxPluginEmbed">the <code>embed</code> element</a>, <a
href="#sandboxPluginObject">the <code>object</code> element</a>,
<a href="#sandboxPluginApplet">the <code>applet</code>
@@ -12556,12 +12585,13 @@
context flag</span> is set on the <span>browsing context</span> for
which the <code>embed</code> element's document is the <span>active
document</span>, then the user agent must render the
- <code>embed</code> element in a manner that conveys that the plugin
- was disabled. The user agent may offer the user the option to
- override the sandbox and instantiate the handler anyway; if the user
- invokes such an option, the user agent must act as if the
- <span>sandboxed plugins browsing context flag</span> was not set for
- the purposes of this element.</p>
+ <code>embed</code> element in a manner that conveys that the
+ <span>plugin</span> was disabled. The user agent may offer the user
+ the option to override the sandbox and instantiate the
+ <span>plugin</span> anyway; if the user invokes such an option, the
+ user agent must act as if the <span>sandboxed plugins browsing
+ context flag</span> was not set for the purposes of this
+ element.</p>
<p class="warning">Plugins are disabled in sandboxed browsing
contexts because they might not honour the restrictions imposed by
@@ -12575,33 +12605,26 @@
context:</p>
<p>When the <code title="attr-embed-src">src</code> attribute is
- set, user agents are expected to find an appropriate handler for the
- specified resource, based on the <span
+ set, user agents are expected to find an appropriate
+ <span>plugin</span> for the specified resource, based on the <span
title="concept-embed-type">content's type</span>, and hand that
- handler the content of the resource. If the handler supports a
- scriptable interface, the <code>HTMLEmbedElement</code> object
- representing the element should expose that interfaces.</p>
+ <span>plugin</span> the content of the resource. If the
+ <span>plugin</span> supports a scriptable interface, the
+ <code>HTMLEmbedElement</code> object representing the element should
+ expose that interfaces.</p>
<p>The download of the resource must <span>delay the <code
title="event-load">load</code> event</span>.</p>
<p>The user agent should pass the names and values of all the
attributes of the <code>embed</code> element that have no namespace
- to the handler used. Any (namespace-less) attribute may be specified
- on the <code>embed</code> element.</p>
+ to the <span>plugin</span> used. Any (namespace-less) attribute may
+ be specified on the <code>embed</code> element.</p>
- <!-- duplicates what's in <object> section below -->
- <p class="note">This specification does not define a mechanism for
- interacting with third-party handlers, as it is expected to be
- user-agent-specific. Some UAs might opt to support a plugin
- mechanism such as the Netscape Plugin API; others may use remote
- content convertors or have built-in support for certain types. <a
- href="#refsNPAPI">[NPAPI]</a></p>
-
<p>The <code>embed</code> element has no <span>fallback
content</span>. If the user agent can't display the specified
resource, e.g. because the given type is not supported, then the
- user agent must use a default handler for the content. (This default
+ user agent must use a default plugin for the content. (This default
could be as simple as saying "Unsupported Format", of course.)</p>
<p>The <dfn title="attr-embed-type"><code>type</code></dfn>
@@ -12624,7 +12647,7 @@
that is the <span>content's type</span>.</li>
<li>Otherwise, the content has no type and there can be no
- appropriate handler for it.</li>
+ appropriate <span>plugin</span> for it.</li>
</ol>
@@ -12638,12 +12661,6 @@
whether the resource is used or not. Not sure how to say it here
though.</p>
- <p>Browsers should take extreme care when interacting with external
- content intended for third-party renderers. When third-party
- software is run with the same privileges as the user agent itself,
- vulnerabilities in the third-party software become as dangerous as
- those in the user agent.</p>
-
<p>The <code>embed</code> element supports <span>dimension
attributes</span>.</p>
@@ -12695,8 +12712,8 @@
<p>The <code>object</code> element can represent an external
resource, which, depending on the type of the resource, will either
be treated as an image, as a nested <span>browsing context</span>,
- or as an external resource to be processed by a third-party software
- package.</p>
+ or as an external resource to be processed by a
+ <span>plugin</span>.</p>
<p>The <dfn title="attr-object-data"><code>data</code></dfn>
attribute, if present, specifies the address of the resource. If
@@ -12732,14 +12749,14 @@
<p>If the <code title="attr-object-classid">classid</code>
attribute is present, and has a value that isn't the empty string,
- then: if the user agent can find a handler suitable according to
+ then: if the user agent can find a <span>plugin</span> suitable according to
the value of the <code title="attr-object-classid">classid</code>
attribute, and <a href="#sandboxPluginObject">handlers aren't
- being sandboxed</a>, then that handler <a
+ being sandboxed</a>, then that <span>plugin</span> <a
href="#object-plugin">should be used</a>, and the value of the
<code title="attr-object-data">data</code> attribute, if any,
- should be passed to the handler. If no suitable handler can be
- found, or if the handler reports an error, jump to the last step
+ should be passed to the <span>plugin</span>. If no suitable <span>plugin</span> can be
+ found, or if the <span>plugin</span> reports an error, jump to the last step
in the overall set of steps (fallback).</p>
<!--
@@ -12763,7 +12780,7 @@
<li><p>If the <code title="attr-object-type">type</code>
attribute is present and its value is not a type that the user
agent supports, and is not a type that the user agent can find a
- handler for, then the user agent may jump to the last step in the
+ <span>plugin</span> for, then the user agent may jump to the last step in the
overall set of steps (fallback) without downloading the content
to examine its real type.</p></li>
@@ -12842,15 +12859,15 @@
<dl class="switch">
<dt>If the <var title="">resource type</var> can be handled by
- a special handler (e.g. a plugin), and <a
- href="#sandboxPluginObject">handlers aren't being
+ a <span>plugin</span> and <a
+ href="#sandboxPluginObject">plugins aren't being
sandboxed</a></dt>
<dd>
<p>The user agent <a href="#object-plugin">should use that
- handler</a> and pass the content of the resource to that
- handler. If the handler reports an error, then jump to the
+ plugin</a> and pass the content of the resource to that
+ <span>plugin</span>. If the <span>plugin</span> reports an error, then jump to the
last step in the overall set of steps (fallback).</p>
</dd>
@@ -12939,12 +12956,12 @@
<li><p>If the <code title="attr-object-data">data</code> attribute
is absent but the <code title="attr-object-type">type</code>
- attribute is present, <a href="#sandboxPluginObject">handlers
- aren't being sandboxed</a>, and the user agent can find a handler
+ attribute is present, <a href="#sandboxPluginObject">plugins
+ aren't being sandboxed</a>, and the user agent can find a <span>plugin</span>
suitable according to the value of the <code
- title="attr-object-type">type</code> attribute, then that handler
- <a href="#object-plugin">should be used</a>. If no suitable handler
- can be found, or if the handler reports an error, jump to the next
+ title="attr-object-type">type</code> attribute, then that <span>plugin</span>
+ <a href="#object-plugin">should be used</a>. If no suitable <span>plugin</span>
+ can be found, or if the <span>plugin</span> reports an error, jump to the next
step (fallback).</p></li>
<li><p>(Fallback.) The <code>object</code> element represents what
@@ -12955,31 +12972,21 @@
</ol>
<p id="object-plugin">When the algorihm above instantiates a
- handler, the user agent should pass the names and values of all the
+ <span>plugin</span>, the user agent should pass the names and values of all the
<span title="concept-param-parameter">parameters</span> given by
<code>param</code> elements that are children of the
- <code>object</code> element to the handler used. If the handler
+ <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
- handler is not a nested <span>browsing context</span>.</p>
+ <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
which the <code>object</code> element's document is the <span>active
document</span>, then the steps above must always act as if they had
- failed to find a handler, even if one would otherwise have been
+ failed to find a <span>plugin</span>, even if one would otherwise have been
used.</p>
- <!-- duplicates what's in <embed> section above -->
- <p class="note">The <code>object</code> element can, in certain
- cases as described above, instantiate third-party handlers. This
- specification does not define a mechanism for interacting with
- third-party handlers, as it is expected to be
- user-agent-specific. Some UAs might opt to support a plugin
- mechanism such as the Netscape Plugin API; others may use remote
- content convertors or have built-in support for certain types. <a
- href="#refsNPAPI">[NPAPI]</a></p>
-
<p>Due to the algorithm above, the contents of <code>object</code>
elements act as <span>fallback content</span>, used only when
referenced resources can't be shown (e.g. because it returned a 404
@@ -13069,7 +13076,7 @@
</dd>
</dl>
- <p>The <code>param</code> element defines parameters for handlers
+ <p>The <code>param</code> element defines parameters for plugins
invoked by <code>object</code> elements.</p>
<p>The <dfn title="attr-param-name"><code>name</code></dfn>
More information about the Commit-Watchers
mailing list