[html5] r1525 - /
whatwg at whatwg.org
whatwg at whatwg.org
Mon May 5 22:15:16 PDT 2008
Author: ianh
Date: 2008-05-05 22:15:16 -0700 (Mon, 05 May 2008)
New Revision: 1525
Modified:
index
source
Log:
[] (0) Support classid=''. Also, factor out the common parts of plugin handling for <object>.
Modified: index
===================================================================
--- index 2008-05-06 04:43:09 UTC (rev 1524)
+++ index 2008-05-06 05:15:16 UTC (rev 1525)
@@ -14198,15 +14198,34 @@
name</a>.
<p>When the element is created, and subsequently whenever the <code
- title=attr-object-data><a href="#data">data</a></code> attribute changes,
- or, if the <code title=attr-object-data><a href="#data">data</a></code>
- attribute is not present, whenever the <code title=attr-object-type><a
+ title=attr-object-classid>classid</code> attribute changes, or, if the
+ <code title=attr-object-classid>classid</code> attribute is not present,
+ whenever the <code title=attr-object-data><a href="#data">data</a></code>
+ attribute changes, or, if neither <code
+ title=attr-object-classid>classid</code> attribute nor the <code
+ title=attr-object-data><a href="#data">data</a></code> attribute are
+ present, whenever the <code title=attr-object-type><a
href="#type6">type</a></code> attribute changes, the user agent must run
the following steps to determine what the <code><a
href="#object">object</a></code> element represents:
<ol>
<li>
+ <p>If the <code title=attr-object-classid>classid</code> attribute is
+ present, then: if the user agent can find a handler suitable according
+ to the value of the <code title=attr-object-classid>classid</code>
+ attribute, 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, jump to the last step in
+ the overall set of steps (fallback).</p>
+ <!--
+ if it starts with "java:", then use the plugin for application/x-java-vm
+ if it starts with "clsid:", then use the plugin for application/x-oleobject
+ -->
+
+
+ <li>
<p>If the <code title=attr-object-data><a href="#data">data</a></code>
attribute is present, then:</p>
@@ -14266,33 +14285,13 @@
<dt>If the resource requires a special handler (e.g. a plugin)
<dd>
- <p>The user agent should find an appropriate handler for the
- specified resource, based on the <em>resource type</em> found in the
- previous step, and pass the content of the resource to that handler.
- If the handler 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="#browsing0">browsing context</a>. If no
- appropriate handler can be found, then jump to step 3 in the overall
- set of steps (fallback).</p>
+ <p>If the user agent has an appropriate handler for the specified
+ resource, based on the <em>resource type</em> found in the previous
+ step, then the user agent <a href="#object-plugin">should use that
+ handler</a> and pass the content of the resource to that handler. If
+ no appropriate handler can be found, then jump to the last step in
+ the overall set of steps (fallback).</p>
- <p>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.</p>
- <!-- duplicates what's in <embed> section above -->
- <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 class=big-issue>this doesn't completely duplicate the navigation
- section, since it handles <param>, etc, but surely some work
- should be done to work with it</p>
-
<dt>If the type of the resource is an <span>XML MIME
type</span><!-- XXX xref -->
@@ -14358,11 +14357,7 @@
href="#type6">type</a></code> attribute is present, and if 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 should be used. If the handler 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="#browsing0">browsing context</a>. If no suitable
+ that handler <a href="#object-plugin">should be used</a>. If no suitable
handler can be found, jump to the next step (fallback).
<li>
@@ -14372,6 +14367,25 @@
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
+ href="#htmlobjectelement">HTMLObjectElement</a></code> object representing
+ the element should expose that interface. The handler is not a nested <a
+ href="#browsing0">browsing context</a>.</p>
+ <!-- duplicates what's in <embed> section above -->
+
+ <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
Modified: source
===================================================================
--- source 2008-05-06 04:43:09 UTC (rev 1524)
+++ source 2008-05-06 05:15:16 UTC (rev 1525)
@@ -12195,14 +12195,37 @@
name</span>.</p>
<p>When the element is created, and subsequently whenever the <code
- title="attr-object-data">data</code> attribute changes, or, if the
- <code title="attr-object-data">data</code> attribute is not present,
- whenever the <code title="attr-object-type">type</code> attribute
- changes, the user agent must run the following steps to determine
- what the <code>object</code> element represents:</p>
+ title="attr-object-classid">classid</code> attribute changes, or, if
+ the <code title="attr-object-classid">classid</code> attribute is
+ not present, whenever the <code title="attr-object-data">data</code>
+ attribute changes, or, if neither <code
+ title="attr-object-classid">classid</code> attribute nor the <code
+ title="attr-object-data">data</code> attribute are present, whenever
+ the <code title="attr-object-type">type</code> attribute changes,
+ the user agent must run the following steps to determine what the
+ <code>object</code> element represents:</p>
<ol>
+ <li>
+
+ <p>If the <code title="attr-object-classid">classid</code>
+ attribute is present, then: if the user agent can find a handler
+ suitable according to the value of the <code
+ title="attr-object-classid">classid</code> attribute, then that
+ handler <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, jump to the last step in the overall set of steps
+ (fallback).</p>
+
+ <!--
+ if it starts with "java:", then use the plugin for application/x-java-vm
+ if it starts with "clsid:", then use the plugin for application/x-oleobject
+ -->
+
+ </li>
+
<li><p>If the <code title="attr-object-data">data</code> attribute
is present, then:</p>
@@ -12272,33 +12295,14 @@
<dd>
- <p>The user agent should find an appropriate handler for the
+ <p>If the user agent has an appropriate handler for the
specified resource, based on the <em>resource type</em> found
- in the previous step, and pass the content of the resource to
- that handler. If the handler 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>. If no appropriate
- handler can be found, then jump to step 3 in the overall set
- of steps (fallback).</p>
+ in the previous step, then the user agent <a
+ href="#object-plugin">should use that handler</a> and pass the
+ content of the resource to that handler. If no appropriate
+ handler can be found, then jump to the last step in the
+ overall set of steps (fallback).</p>
- <p>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.</p>
-
- <!-- duplicates what's in <embed> section above -->
- <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 class="big-issue">this doesn't completely duplicate the
- navigation section, since it handles <param>, etc, but
- surely some work should be done to work with it</p>
-
</dd>
@@ -12371,16 +12375,15 @@
</ol>
+ </li>
+
<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, and if the user agent can find a handler
suitable according to the value of the <code
title="attr-object-type">type</code> attribute, then that handler
- should be used. If the handler 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>. If no suitable handler can be found,
- jump to the next step (fallback).</p></li>
+ <a href="#object-plugin">should be used</a>. If no suitable handler
+ can be found, jump to the next step (fallback).</p></li>
<li><p>(Fallback.) The <code>object</code> element represents what
the element's contents represent, ignoring any leading
@@ -12389,6 +12392,25 @@
</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>param</code> elements that are children of the
+ <code>object</code> element to the handler used. If the handler
+ 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>
+
+ <!-- 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
More information about the Commit-Watchers
mailing list