[html5] r1816 - [] (0) remaining URLification
whatwg at whatwg.org
whatwg at whatwg.org
Fri Jun 27 01:03:37 PDT 2008
Author: ianh
Date: 2008-06-27 01:03:36 -0700 (Fri, 27 Jun 2008)
New Revision: 1816
Modified:
index
source
Log:
[] (0) remaining URLification
Modified: index
===================================================================
--- index 2008-06-27 06:24:54 UTC (rev 1815)
+++ index 2008-06-27 08:03:36 UTC (rev 1816)
@@ -39996,8 +39996,7 @@
providing a tree-based approach to document state). Such UI models should
be based upon the single <a href="#undo-transaction">undo transaction
history</a> described in this section, however, such that to a script
- there is no detectable difference.</p>
- <!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXURL \(url\|uri\|iri\) -->
+ there is no detectable difference.
<h3 id=command><span class=secno>6.10 </span>Command APIs</h3>
@@ -40089,8 +40088,7 @@
<dd><strong>Value:</strong> The string "<code title="">true</code>" if the
expression given for the "State" above is true, the string "<code
- title="">false</code>" otherwise.</dd>
- <!-- XXXURL change to URL -->
+ title="">false</code>" otherwise.
<dt><dfn id=createlink
title=command-createLink><code>createLink</code></dfn>
@@ -40104,8 +40102,8 @@
existing <code><a href="#a">a</a></code> element, then if the <var
title="">showUI</var> argument is present and has the value false, then
the value of the <var title="">value</var> argument must be used as the
- URI of the link. Otherwise, the user should be prompted for the URI of
- the link.
+ <a href="#url">URL</a> of the link. Otherwise, the user should be
+ prompted for the URL of the link.
<dd><strong>Enabled When:</strong> The document is <a href="#ready">ready
for editing host commands</a>.
@@ -40196,8 +40194,7 @@
<dd><strong>State:</strong> Always false.
<dd><strong>Value:</strong> Always the string "<code
- title="">false</code>".</dd>
- <!-- XXXURL change to URL -->
+ title="">false</code>".
<dt><dfn id=insertimage
title=command-insertImage><code>insertImage</code></dfn>
@@ -40211,8 +40208,8 @@
an existing <code><a href="#img">img</a></code> element, then if the <var
title="">showUI</var> argument is present and has the value false, then
the value of the <var title="">value</var> argument must be used as the
- URI of the image. Otherwise, the user should be prompted for the URI of
- the image.
+ <a href="#url">URL</a> of the image. Otherwise, the user should be
+ prompted for the URL of the image.
<dd><strong>Enabled When:</strong> The document is <a href="#ready">ready
for editing host commands</a>.
@@ -40608,42 +40605,42 @@
void <a href="#addeventsource" title=dom-RemoteEventTarget-addEventSource>addEventSource</a>(in DOMString src);
void <a href="#removeeventsource" title=dom-RemoteEventTarget-removeEventSource>removeEventSource</a>(in DOMString src);
};</pre>
- <!-- XXXURL change to URL; algorithms? -->
<p>When the <dfn id=addeventsource
title=dom-RemoteEventTarget-addEventSource><code>addEventSource(<var
- title="">src</var>)</code></dfn> method is invoked, the user agent must
- add the URI specified in <var title="">src</var> to the <a
+ title="">src</var>)</code></dfn> method is invoked, the user agent must <a
+ href="#resolve" title="resolve a url">resolve</a> the <a
+ href="#url">URL</a> specified in <var title="">src</var>, and if that
+ succeeds, add the resulting <a href="#absolute">absolute URL</a> to the <a
href="#list-of3" title=concept-event-source-list>list of event sources</a>
- for that object. The same URI can be registered multiple times.</p>
- <!-- XXXURL change to URL -->
+ for that object. The same URL can be registered multiple times. If the URL
+ fails to resolve, then the user agent must raise a <code>SYNTAX_ERR</code>
+ exception.
<p>When the <dfn id=removeeventsource
title=dom-RemoteEventTarget-removeEventSource><code>removeEventSource(<var
- title="">src</var>)</code></dfn> method is invoked, the user agent must
- remove the URI specified in <var title="">src</var> from the <a
- href="#list-of3" title=concept-event-source-list>list of event sources</a>
- for that object. If the same URI has been registered multiple times,
- removing it must remove only one instance of that URI for each invocation
- of the <code title=removeEventSource>removeEventSource()</code> method.</p>
- <!-- XXXURL algorithms -->
+ title="">src</var>)</code></dfn> method is invoked, the user agent must <a
+ href="#resolve" title="resolve a url">resolve</a> the <a
+ href="#url">URL</a> specified in <var title="">src</var>, and if that
+ succeeds, remove the resulting <a href="#absolute">absolute URL</a> from
+ the <a href="#list-of3" title=concept-event-source-list>list of event
+ sources</a> for that object. If the same URI has been registered multiple
+ times, removing it must remove only one instance of that URI for each
+ invocation of the <code title=removeEventSource>removeEventSource()</code>
+ method. If the URL fails to resolve, the user agent does nothing.
- <p>Relative URIs must be resolved relative to <span
- class=big-issue>...</span>.
-
<h4 id=connecting><span class=secno>7.2.2 </span>Connecting to an event
stream</h4>
<p>Each object implementing the <code>EventTarget</code> and <code><a
href="#remoteeventtarget0">RemoteEventTarget</a></code> interfaces has a
<dfn id=list-of3 title=concept-event-source-list>list of event
- sources</dfn> that are registered for that object.</p>
- <!-- XXXURL change to URL; algorithms for 'fetch'? -->
+ sources</dfn> that are registered for that object.
<p>When a new URI is added to this list, the user agent should, as soon as
- all currently executing scripts (if any) have finished executing, and if
- the specified URI isn't removed from the list before they do so, fetch the
- resource identified by that URI.
+ all currently executing scripts (if any) have finished
+ executing<!-- XXX queue -->, and if the specified URL isn't removed from
+ the list before they do so, fetch the resource identified by that URL.
<p>When an event source is removed from the list of event sources for an
object, if that resource is still being fetched, then the relevant
@@ -40668,10 +40665,9 @@
<li>The <dfn id=last-event title=concept-event-stream-last-event-id>last
event ID string</dfn>. This must initially be the empty string.
</ul>
- <!-- XXXURL change to URL -->
<p>In general, the semantics of the transport protocol specified by the
- URIs for the event sources must be followed, including HTTP caching rules.
+ URLs for the event sources must be followed, including HTTP caching rules.
<p>For HTTP connections, the <code title="">Accept</code> header may be
included; if included, it must contain only formats of event framing that
@@ -40737,21 +40733,19 @@
<p>HTTP 300 Multiple Choices responses should be handled automatically if
possible (treating the responses as if they were 302 Found responses
pointing to the appropriate resource), and otherwise must be treated as
- HTTP 404 responses.</p>
- <!-- XXXURL change to URL -->
+ HTTP 404 responses.
<p>HTTP 301 Moved Permanently responses must cause the user agent to
- reconnect using the new server specified URI instead of the previously
- specified URI for all subsequent requests for this event source. (It
- doesn't affect other event sources with the same URI unless they also
+ reconnect using the new server specified URL instead of the previously
+ specified URL for all subsequent requests for this event source. (It
+ doesn't affect other event sources with the same URL unless they also
receive 301 responses, and it doesn't affect future sessions, e.g. if the
- page is reloaded.)</p>
- <!-- XXXURL change to URL -->
+ page is reloaded.)
<p>HTTP 302 Found, 303 See Other, and 307 Temporary Redirect responses must
- cause the user agent to connect to the new server-specified URI, but if
+ cause the user agent to connect to the new server-specified URL, but if
the user agent needs to again request the resource at a later point, it
- must return to the previously specified URI for this event source.
+ must return to the previously specified URL for this event source.
<p>HTTP 304 Not Modified responses should be handled like HTTP 200 OK
responses, with the content coming from the user agent cache. A new
@@ -40928,8 +40922,6 @@
href="http://www.w3.org/TR/REC-xml-names/#NT-NCName">NCName</a>, set the
<var title="">data</var> buffer and the <var title="">event name</var>
buffer to the empty string and abort these steps.
- </li>
- <!-- XXXURL change to URL -->
<li>
<p>Otherwise, create an event that uses the <code><a
@@ -40940,7 +40932,7 @@
attribute must be set to the value of the <var title="">data</var>
buffer, the <code title=dom-MessageEvent-origin><a
href="#origin1">origin</a></code> attribute must be set to the <a
- href="#origin0">origin</a> of the event stream's URI, the <code
+ href="#origin0">origin</a> of the event stream's URL, the <code
title=dom-MessageEvent-lastEventId><a
href="#lasteventid">lastEventId</a></code> attribute must be set to the
<span>last event ID string</span> of the event source, and the <code
@@ -41053,8 +41045,7 @@
<p>Legacy proxy servers are known to, in certain cases, drop HTTP
connections after a short timeout. To protect against such proxy servers,
authors can include a comment line (one starting with a ':' character)
- every 15 seconds or so.</p>
- <!-- XXXURL change to URL -->
+ every 15 seconds or so.
<p>Authors wishing to relate event source connections to each other or to
specific documents previously served might find that relying on IP
@@ -41062,7 +41053,7 @@
addresses (due to having multiple proxy servers) and individual IP
addresses can have multiple clients (due to sharing a proxy server). It is
better to include a unique identifier in the document when it is served
- and then pass that identifier as part of the URI in the <code
+ and then pass that identifier as part of the URL in the <code
title=attr-event-source-src><a href="#src11">src</a></code> attribute of
the <code><a href="#event-source">event-source</a></code> element.
@@ -41938,8 +41929,9 @@
<ol>
<li>
- <p>If the value of the <var title="">targetOrigin</var> argument is
- neither a single U+002A ASTERISK character ("*") nor a valid URI or IRI,
+ <p>If the value of the <var title="">targetOrigin</var> argument is not a
+ single U+002A ASTERISK character ("*"), and <a href="#parse0"
+ title="parse a url">parsing</a> it as a <a href="#url">URL</a> fails,
then throw a <code>SYNTAX_ERR</code> exception and abort the overall set
of steps. <a href="#refsRFC3490">[RFC3986]</a> <a
href="#refsRFC3490">[RFC3987]</a></p>
@@ -46682,21 +46674,18 @@
href="#html-namespace0">HTML namespace</a>. Append it to the
<code>Document</code> object. Put this element in the <a
href="#stack">stack of open elements</a>.</p>
- <!-- XXXURL change to URL; algorithms (with care) -->
- <p id=parser-appcache>If the token has an attribute "manifest", then run
- the <a href="#application2"
+
+ <p id=parser-appcache>If the token has an attribute "manifest", then <a
+ href="#resolve" title="resolve a url">resolve</a> the value of that
+ attribute to an <a href="#absolute">absolute URL</a>, and if that is
+ successful, run the <a href="#application2"
title=concept-appcache-init-with-attribute>application cache selection
- algorithm</a> with the value of that attribute as the manifest URI,
- resolving relative URIs according to section 5.1 of RFC3986 as if there
- was no base URI embedded in content (i.e. relative to the base URI from
- the encapsulating entity or the URI used to retrieve the entity).
- Otherwise, run the <a href="#application3"
+ algorithm</a> with the resulting <a href="#absolute">absolute URL</a>.
+ Otherwise, if there is no such attribute or resolving it fails, run the
+ <a href="#application3"
title=concept-appcache-init-no-attribute>application cache selection
algorithm</a> with no manifest. <a href="#refsRFC3986">[RFC3986]</a></p>
- <!-- XXXURL when dealing with
- microsyntaxes-urls, hoist all this into that section so we can get
- rid of "URI" here -->
-
+
<p>Switch the <span>insertion mode</span> to "<a href="#before5"
title="insertion mode: before head">before head</a>".</p>
@@ -52768,7 +52757,6 @@
some sort of markup to tell google _not_ to index a particular part of the site
-drop down menu with URIs to replace the silly <select> hacks.
http://www.cs.tut.fi/~jkorpela/html/em.html
@@ -52982,7 +52970,7 @@
<h2>Tree and List Widgets</h2>
- click item to go uri
+ click item to go url
doube click to submit form with value
sort list by any column
specify column headers, column sort types
@@ -53205,7 +53193,7 @@
file.read();
var file = window.saveAsFile(); // throws up UI
file.write();
-...or something? Or use data: URIs and right-click-to-save?
+...or something? Or use data: URLs and right-click-to-save?
http://lxr.mozilla.org/mozilla/source/dom/public/idl/html/nsIDOMNSHTMLDocument.idl
@@ -53404,7 +53392,7 @@
how to handle 205 reset content responses and other HTTP codes in
response to link clicks, link clicks with target="" attributes,
-window.open(), the user typing a URI in the URL bar, etc.
+window.open(), the user typing a URL in the URL bar, etc.
XXX Native code for fast sorting of many data?
@@ -53925,7 +53913,7 @@
<dt><dfn title="attr-command-icon"><code>icon</code></dfn></dt>
- <dd>A URI to the command's Icon. If the attribute is not specified,
+ <dd>A URL to the command's Icon. If the attribute is not specified,
then the command has no Icon.</dd>
<dt><dfn title="attr-command-onclick"><code>onclick</code></dfn></dt>
Modified: source
===================================================================
--- source 2008-06-27 06:24:54 UTC (rev 1815)
+++ source 2008-06-27 08:03:36 UTC (rev 1816)
@@ -37682,7 +37682,6 @@
- <!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXURL \(url\|uri\|iri\) -->
<h3>Command APIs</h3>
@@ -37775,7 +37774,6 @@
if the expression given for the "State" above is true, the string
"<code title="">false</code>" otherwise.</dd>
- <!-- XXXURL change to URL -->
<dt><dfn title="command-createLink"><code>createLink</code></dfn></dt>
<dd><strong>Action:</strong> The user agent must act as if the user
had requested that the selection <a
@@ -37786,8 +37784,8 @@
element or modifies an existing <code>a</code> element, then if the
<var title="">showUI</var> argument is present and has the value
false, then the value of the <var title="">value</var> argument
- must be used as the URI of the link. Otherwise, the user should be
- prompted for the URI of the link.</dd>
+ must be used as the <span>URL</span> of the link. Otherwise, the
+ user should be prompted for the URL of the link.</dd>
<dd><strong>Enabled When:</strong> The document is <span>ready for
editing host commands</span>.</dd>
<dd><strong>Indeterminate When:</strong> Never.</dd>
@@ -37853,7 +37851,6 @@
<dd><strong>State:</strong> Always false.</dd>
<dd><strong>Value:</strong> Always the string "<code title="">false</code>".</dd>
- <!-- XXXURL change to URL -->
<dt><dfn title="command-insertImage"><code>insertImage</code></dfn></dt>
<dd><strong>Action:</strong> The user agent must act as if the user
had requested that the selection <a
@@ -37862,11 +37859,11 @@
(or, again, unwrapped, or have that semantic inserted or removed,
as defined by the UA). If the user agent creates an
<code>img</code> element or modifies an existing <code>img</code>
- element, then if the <var title="">showUI</var> argument is
- present and has the value false, then the value of the <var
- title="">value</var> argument must be used as the URI of the
- image. Otherwise, the user should be prompted for the URI of the
- image.</dd>
+ element, then if the <var title="">showUI</var> argument is present
+ and has the value false, then the value of the <var
+ title="">value</var> argument must be used as the <span>URL</span>
+ of the image. Otherwise, the user should be prompted for the URL of
+ the image.</dd>
<dd><strong>Enabled When:</strong> The document is <span>ready for
editing host commands</span>.</dd>
<dd><strong>Indeterminate When:</strong> Never.</dd>
@@ -38164,30 +38161,30 @@
void <span title="dom-RemoteEventTarget-removeEventSource">removeEventSource</span>(in DOMString src);
};</pre>
- <!-- XXXURL change to URL; algorithms? -->
<p>When the <dfn
title="dom-RemoteEventTarget-addEventSource"><code>addEventSource(<var
title="">src</var>)</code></dfn> method is invoked, the user agent
- must add the URI specified in <var title="">src</var> to the <span
- title="concept-event-source-list">list of event sources</span> for
- that object. The same URI can be registered multiple times.</p>
+ must <span title="resolve a url">resolve</span> the <span>URL</span>
+ specified in <var title="">src</var>, and if that succeeds, add the resulting <span>absolute URL</span>
+ to the <span title="concept-event-source-list">list of event
+ sources</span> for that object. The same URL can be registered
+ multiple times. If the URL fails to resolve, then the user agent
+ must raise a <code>SYNTAX_ERR</code> exception.</p>
- <!-- XXXURL change to URL -->
<p>When the <dfn
title="dom-RemoteEventTarget-removeEventSource"><code>removeEventSource(<var
title="">src</var>)</code></dfn> method is invoked, the user agent
- must remove the URI specified in <var title="">src</var> from the
- <span title="concept-event-source-list">list of event sources</span>
- for that object. If the same URI has been registered multiple
- times, removing it must remove only one instance of that URI for
- each invocation of the <code
- title="removeEventSource">removeEventSource()</code> method.</p>
+ must <span title="resolve a url">resolve</span> the <span>URL</span>
+ specified in <var title="">src</var>, and if that succeeds, remove
+ the resulting <span>absolute URL</span> from the <span
+ title="concept-event-source-list">list of event sources</span> for
+ that object. If the same URI has been registered multiple times,
+ removing it must remove only one instance of that URI for each
+ invocation of the <code
+ title="removeEventSource">removeEventSource()</code> method. If the
+ URL fails to resolve, the user agent does nothing.</p>
- <!-- XXXURL algorithms -->
- <p>Relative URIs must be resolved relative to <span
- class="big-issue">...</span>.</p>
-
<h4>Connecting to an event stream</h4>
<p>Each object implementing the <code>EventTarget</code> and
@@ -38195,11 +38192,11 @@
title="concept-event-source-list">list of event sources</dfn> that
are registered for that object.</p>
- <!-- XXXURL change to URL; algorithms for 'fetch'? -->
<p>When a new URI is added to this list, the user agent should, as
soon as all currently executing scripts (if any) have finished
- executing, and if the specified URI isn't removed from the list
- before they do so, fetch the resource identified by that URI.</p>
+ executing<!-- XXX queue -->, and if the specified URL isn't removed
+ from the list before they do so, fetch the resource identified by
+ that URL.</p>
<p>When an event source is removed from the list of event sources
for an object, if that resource is still being fetched, then the
@@ -38228,9 +38225,8 @@
</ul>
- <!-- XXXURL change to URL -->
<p>In general, the semantics of the transport protocol specified by
- the URIs for the event sources must be followed, including HTTP
+ the URLs for the event sources must be followed, including HTTP
caching rules.</p>
<p>For HTTP connections, the <code title="">Accept</code> header may
@@ -38300,20 +38296,18 @@
302 Found responses pointing to the appropriate resource), and
otherwise must be treated as HTTP 404 responses.</p>
- <!-- XXXURL change to URL -->
<p>HTTP 301 Moved Permanently responses must cause the user agent to
- reconnect using the new server specified URI instead of the
- previously specified URI for all subsequent requests for this event
- source. (It doesn't affect other event sources with the same URI
+ reconnect using the new server specified URL instead of the
+ previously specified URL for all subsequent requests for this event
+ source. (It doesn't affect other event sources with the same URL
unless they also receive 301 responses, and it doesn't affect future
sessions, e.g. if the page is reloaded.)</p>
- <!-- XXXURL change to URL -->
<p>HTTP 302 Found, 303 See Other, and 307 Temporary Redirect
responses must cause the user agent to connect to the new
- server-specified URI, but if the user agent needs to again request
+ server-specified URL, but if the user agent needs to again request
the resource at a later point, it must return to the previously
- specified URI for this event source.</p>
+ specified URL for this event source.</p>
<p>HTTP 304 Not Modified responses should be handled like HTTP 200
OK responses, with the content coming from the user agent cache. A
@@ -38510,7 +38504,6 @@
name</var> buffer to the empty string and abort these
steps.</p></li>
- <!-- XXXURL change to URL -->
<li><p>Otherwise, create an event that uses the
<code>MessageEvent</code> interface, with the event name <code
title="event-message">message</code>, which does not bubble, is
@@ -38518,7 +38511,7 @@
title="dom-MessageEvent-data">data</code> attribute must be set to
the value of the <var title="">data</var> buffer, the <code
title="dom-MessageEvent-origin">origin</code> attribute must be set
- to the <span>origin</span> of the event stream's URI, the <code
+ to the <span>origin</span> of the event stream's URL, the <code
title="dom-MessageEvent-lastEventId">lastEventId</code> attribute
must be set to the <span>last event ID string</span> of the event
source, and the <code title="dom-MessageEvent-source">source</code>
@@ -38636,7 +38629,6 @@
servers, authors can include a comment line (one starting with a ':'
character) every 15 seconds or so.</p>
- <!-- XXXURL change to URL -->
<p>Authors wishing to relate event source connections to each other
or to specific documents previously served might find that relying
on IP addresses doesn't work, as individual clients can have
@@ -38644,7 +38636,7 @@
individual IP addresses can have multiple clients (due to sharing a
proxy server). It is better to include a unique identifier in the
document when it is served and then pass that identifier as part of
- the URI in the <code title="attr-event-source-src">src</code>
+ the URL in the <code title="attr-event-source-src">src</code>
attribute of the <code>event-source</code> element.</p>
<p>Implementations that support HTTP's per-server connection
@@ -39544,10 +39536,10 @@
<li>
<p>If the value of the <var title="">targetOrigin</var> argument
- is neither a single U+002A ASTERISK character ("*") nor a valid
- URI or IRI, then throw a <code>SYNTAX_ERR</code> exception and
- abort the overall set of steps. <a
- href="#refsRFC3490">[RFC3986]</a> <a
+ is not a single U+002A ASTERISK character ("*"), and <span
+ title="parse a url">parsing</span> it as a <span>URL</span> fails,
+ then throw a <code>SYNTAX_ERR</code> exception and abort the
+ overall set of steps. <a href="#refsRFC3490">[RFC3986]</a> <a
href="#refsRFC3490">[RFC3987]</a></p>
</li>
@@ -43797,20 +43789,17 @@
object. Put this element in the <span>stack of open
elements</span>.</p>
- <!-- XXXURL change to URL; algorithms (with care) -->
<p id="parser-appcache">If the token has an attribute "manifest",
- then run the <span
+ then <span title="resolve a url">resolve</span> the value of that
+ attribute to an <span>absolute URL</span>, and if that is
+ successful, run the <span
title="concept-appcache-init-with-attribute">application cache
- selection algorithm</span> with the value of that attribute as the
- manifest URI, resolving relative URIs according to section 5.1 of
- RFC3986 as if there was no base URI embedded in content
- (i.e. relative to the base URI from the encapsulating entity or
- the URI used to retrieve the entity). Otherwise, run the <span
+ selection algorithm</span> with the resulting <span>absolute
+ URL</span>. Otherwise, if there is no such attribute or resolving
+ it fails, run the <span
title="concept-appcache-init-no-attribute">application cache
selection algorithm</span> with no manifest. <a
- href="#refsRFC3986">[RFC3986]</a></p><!-- XXXURL when dealing with
- microsyntaxes-urls, hoist all this into that section so we can get
- rid of "URI" here -->
+ href="#refsRFC3986">[RFC3986]</a></p>
<p>Switch the <span>insertion mode</span> to "<span
title="insertion mode: before head">before head</span>".</p>
@@ -47987,7 +47976,6 @@
some sort of markup to tell google _not_ to index a particular part of the site
-drop down menu with URIs to replace the silly <select> hacks.
http://www.cs.tut.fi/~jkorpela/html/em.html
@@ -48201,7 +48189,7 @@
<h2>Tree and List Widgets</h2>
- click item to go uri
+ click item to go url
doube click to submit form with value
sort list by any column
specify column headers, column sort types
@@ -48424,7 +48412,7 @@
file.read();
var file = window.saveAsFile(); // throws up UI
file.write();
-...or something? Or use data: URIs and right-click-to-save?
+...or something? Or use data: URLs and right-click-to-save?
http://lxr.mozilla.org/mozilla/source/dom/public/idl/html/nsIDOMNSHTMLDocument.idl
@@ -48623,7 +48611,7 @@
how to handle 205 reset content responses and other HTTP codes in
response to link clicks, link clicks with target="" attributes,
-window.open(), the user typing a URI in the URL bar, etc.
+window.open(), the user typing a URL in the URL bar, etc.
XXX Native code for fast sorting of many data?
@@ -49144,7 +49132,7 @@
<dt><dfn title="attr-command-icon"><code>icon</code></dfn></dt>
- <dd>A URI to the command's Icon. If the attribute is not specified,
+ <dd>A URL to the command's Icon. If the attribute is not specified,
then the command has no Icon.</dd>
<dt><dfn title="attr-command-onclick"><code>onclick</code></dfn></dt>
More information about the Commit-Watchers
mailing list