[html5] r3905 - [] (0) profile='' processing; example for <object>; add link to research for dia [...]
whatwg at whatwg.org
whatwg at whatwg.org
Fri Sep 18 13:30:37 PDT 2009
Author: ianh
Date: 2009-09-18 13:30:36 -0700 (Fri, 18 Sep 2009)
New Revision: 3905
Modified:
index
source
Log:
[] (0) profile='' processing; example for <object>; add link to research for dialog suggestions
Modified: index
===================================================================
--- index 2009-09-18 09:47:36 UTC (rev 3904)
+++ index 2009-09-18 20:30:36 UTC (rev 3905)
@@ -20790,8 +20790,33 @@
</div>
+ <div class=example>
+ <p>The following example shows how the <code><a href=#the-param-element>param</a></code> element
+ can be used to pass a parameter to a plugin, in this case the Flash
+ plugin.</p>
+ <pre><!DOCTYPE HTML>
+<html lang="en">
+ <head>
+ <title>Flash test page</title>
+ </head>
+ <body>
+ <p>
+ <object type="application/x-shockwave-flash">
+ <strong><param name=movie value="http://www.macromedia.com/shockwave/download/triggerpages_mmcom/flash.swf"></strong>
+ This page requires the use of a proprietary technology. Since you
+ have not installed the software product required to view this
+ page, you should try visiting another site that instead uses open
+ vendor-neutral technologies.
+ </object>
+ </p>
+ </body>
+</html></pre>
+
+ </div>
+
+
<h4 id=video><span class=secno>4.8.7 </span>The <dfn><code>video</code></dfn> element</h4>
<dl class=element><dt>Categories</dt>
@@ -42904,6 +42929,8 @@
<h4 id=conversations><span class=secno>4.12.2 </span>Conversations</h4>
+ <!-- http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-September/022576.html -->
+
<p>This specification does not define a specific element for marking
up conversations, meeting minutes, chat transcripts, dialogues in
screenplays, instant message logs, and other situations where
@@ -74258,17 +74285,26 @@
<p>When the attribute would be used as a globally unique name, the
user agent should instead always assume that all known profiles
apply to all pages, and should therefore apply the conventions of
- all known metadata profiles to the document.</p>
+ all known metadata profiles to the document, ignoring the value of
+ the attribute.</p>
<p>When the attribute's value would be handled as a <a href=#url>URL</a>
- and dereferenced, the user agent may <a href=#resolve-a-url title="resolve a
- url">resolve</a> the attribute's value, and if that is
- successful, may then <a href=#fetch>fetch</a> the resulting <a href=#absolute-url>absolute
- URL</a> and apply the appropriate processing.</p>
+ and dereferenced, the user agent must use the following steps:</p>
- <p>The <dfn id=dom-head-profile title=dom-head-profile><code>profile</code></dfn> IDL
+ <ol><li><p><a href=#split-a-string-on-spaces title="split a string on spaces">Split on
+ spaces</a> the the value of the <code title=attr-meta-profile>profile</code> attribute.</li>
+
+ <li><p><a href=#resolve-a-url title="resolve a url">Resolve</a> each resulting
+ token relative to the <code><a href=#meta>meta</a></code> element.</li>
+
+ <li><p>For each token that is successfully resolved,
+ <a href=#fetch>fetch</a> the resulting <a href=#absolute-url>absolute URL</a> and
+ apply the appropriate processing.</li>
+
+ </ol><p>The <dfn id=dom-head-profile title=dom-head-profile><code>profile</code></dfn> IDL
attribute of the <code><a href=#the-head-element-0>head</a></code> element must <a href=#reflect>reflect</a>
- the content attribute of the same name.</p>
+ the content attribute of the same name, as if the attribute's value
+ was just a string. (In other words, the value is not <a href=#resolve-a-url title="resolve a url">resolved</a> in any way on getting.)</p>
<hr><pre class=idl>[Supplemental]
interface <a href=#htmlhrelement>HTMLHRElement</a> {
Modified: source
===================================================================
--- source 2009-09-18 09:47:36 UTC (rev 3904)
+++ source 2009-09-18 20:30:36 UTC (rev 3905)
@@ -22309,8 +22309,33 @@
</div>
+ <div class="example">
+ <p>The following example shows how the <code>param</code> element
+ can be used to pass a parameter to a plugin, in this case the Flash
+ plugin.</p>
+ <pre><!DOCTYPE HTML>
+<html lang="en">
+ <head>
+ <title>Flash test page</title>
+ </head>
+ <body>
+ <p>
+ <object type="application/x-shockwave-flash">
+ <strong><param name=movie value="http://www.macromedia.com/shockwave/download/triggerpages_mmcom/flash.swf"></strong>
+ This page requires the use of a proprietary technology. Since you
+ have not installed the software product required to view this
+ page, you should try visiting another site that instead uses open
+ vendor-neutral technologies.
+ </object>
+ </p>
+ </body>
+</html></pre>
+
+ </div>
+
+
<h4 id="video">The <dfn><code>video</code></dfn> element</h4>
<dl class="element">
@@ -47884,6 +47909,8 @@
<h4>Conversations</h4>
+ <!-- http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-September/022576.html -->
+
<p>This specification does not define a specific element for marking
up conversations, meeting minutes, chat transcripts, dialogues in
screenplays, instant message logs, and other situations where
@@ -88125,17 +88152,32 @@
<p>When the attribute would be used as a globally unique name, the
user agent should instead always assume that all known profiles
apply to all pages, and should therefore apply the conventions of
- all known metadata profiles to the document.</p>
+ all known metadata profiles to the document, ignoring the value of
+ the attribute.</p>
<p>When the attribute's value would be handled as a <span>URL</span>
- and dereferenced, the user agent may <span title="resolve a
- url">resolve</span> the attribute's value, and if that is
- successful, may then <span>fetch</span> the resulting <span>absolute
- URL</span> and apply the appropriate processing.</p>
+ and dereferenced, the user agent must use the following steps:</p>
+ <ol>
+
+ <li><p><span title="split a string on spaces">Split on
+ spaces</span> the the value of the <code
+ title="attr-meta-profile">profile</code> attribute.</p></li>
+
+ <li><p><span title="resolve a url">Resolve</span> each resulting
+ token relative to the <code>meta</code> element.</p></li>
+
+ <li><p>For each token that is successfully resolved,
+ <span>fetch</span> the resulting <span>absolute URL</span> and
+ apply the appropriate processing.</p></li>
+
+ </ol>
+
<p>The <dfn title="dom-head-profile"><code>profile</code></dfn> IDL
attribute of the <code>head</code> element must <span>reflect</span>
- the content attribute of the same name.</p>
+ the content attribute of the same name, as if the attribute's value
+ was just a string. (In other words, the value is not <span
+ title="resolve a url">resolved</span> in any way on getting.)</p>
<hr>
More information about the Commit-Watchers
mailing list