[html5] r1791 - [acgiowrt] (2) Define 'URL' and 'valid U [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Jun 23 17:21:04 PDT 2008
Author: ianh
Date: 2008-06-23 17:21:03 -0700 (Mon, 23 Jun 2008)
New Revision: 1791
Modified:
index
source
Log:
[acgiowrt] (2) Define 'URL' and 'valid URL'. Define 'script document context'. Introduce the term 'script browsing context' for the existing concept of 'browsing context associated with a script execution context' and use that term where appropriate. Define origin of onfoo='' scripts. Fix xref errors. Minor editorial fixes.
Modified: index
===================================================================
--- index 2008-06-19 09:27:25 UTC (rev 1790)
+++ index 2008-06-24 00:21:03 UTC (rev 1791)
@@ -25,7 +25,7 @@
<h1 id=html-5>HTML 5</h1>
- <h2 class="no-num no-toc" id=draft>Draft Recommendation — 19 June
+ <h2 class="no-num no-toc" id=draft>Draft Recommendation — 24 June
2008</h2>
<p>You can take part in this work. <a
@@ -213,7 +213,10 @@
<li><a href="#urls"><span class=secno>2.3 </span>URLs</a>
<ul class=toc>
- <li><a href="#interfaces"><span class=secno>2.3.1 </span>Interfaces
+ <li><a href="#terminology0"><span class=secno>2.3.1
+ </span>Terminology</a>
+
+ <li><a href="#interfaces"><span class=secno>2.3.2 </span>Interfaces
for URI manipulation</a>
</ul>
@@ -2681,6 +2684,40 @@
<h3 id=urls><span class=secno>2.3 </span>URLs</h3>
<!-- XXXURL -->
+ <p class=big-issue>The text in this section is not yet integrated with the
+ rest of the specification.
+
+ <h4 id=terminology0><span class=secno>2.3.1 </span>Terminology</h4>
+
+ <p>A <dfn id=url>URL</dfn> is a string used to identify a resource. A <a
+ href="#url">URL</a> is always associated with a <code>Document</code>,
+ either explicitly when the URL is created or defined; or through a DOM
+ node, in which case the associated <code>Document</code> is the node's
+ <code>Document</code>; or through a script, in which case the associated
+ <code>Document</code> is the script's <a href="#script4">script document
+ context</a>.
+
+ <p>A <a href="#url">URL</a> is a <dfn id=valid>valid URL</dfn> if at least
+ one of the following conditions holds:
+
+ <ul>
+ <li>
+ <p>The <a href="#url">URL</a> is a valid URI.
+
+ <li>
+ <p>The <a href="#url">URL</a> is a valid IRI and it has no query
+ component.
+
+ <li>
+ <p>The <a href="#url">URL</a> is a valid IRI and its query component
+ contains no unescaped non-ASCII characters.
+
+ <li>
+ <p>The <a href="#url">URL</a> is a valid IRI and the <a
+ href="#character1" title="document's character encoding">character
+ encoding</a> of the URL's <code>Document</code> is UTF-8.
+ </ul>
+
<div class=big-issue>
<p>This section will do the following:</p>
@@ -2785,7 +2822,7 @@
</div>
<!-- XXXURL change to URL -->
- <h4 id=interfaces><span class=secno>2.3.1 </span>Interfaces for URI
+ <h4 id=interfaces><span class=secno>2.3.2 </span>Interfaces for URI
manipulation</h4>
<!-- XXXURL change to URL -->
@@ -3078,7 +3115,7 @@
<h5 id=unsigned><span class=secno>2.4.3.1. </span>Unsigned integers</h5>
- <p>A string is a <dfn id=valid>valid non-negative integer</dfn> if it
+ <p>A string is a <dfn id=valid0>valid non-negative integer</dfn> if it
consists of one of more characters in the range U+0030 DIGIT ZERO (0) to
U+0039 DIGIT NINE (9).
@@ -3139,7 +3176,7 @@
<h5 id=signed><span class=secno>2.4.3.2. </span>Signed integers</h5>
- <p>A string is a <dfn id=valid0>valid integer</dfn> if it consists of one
+ <p>A string is a <dfn id=valid1>valid integer</dfn> if it consists of one
of more characters in the range U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE
(9), optionally prefixed with a U+002D HYPHEN-MINUS ("-") character.
@@ -3217,7 +3254,7 @@
<h5 id=real-numbers><span class=secno>2.4.3.3. </span>Real numbers</h5>
- <p>A string is a <dfn id=valid1>valid floating point number</dfn> if it
+ <p>A string is a <dfn id=valid2>valid floating point number</dfn> if it
consists of one of more characters in the range U+0030 DIGIT ZERO (0) to
U+0039 DIGIT NINE (9), optionally with a single U+002E FULL STOP (".")
character somewhere (either before these numbers, in between two numbers,
@@ -3343,7 +3380,7 @@
<code><a href="#progress">progress</a></code> and <code><a
href="#meter">meter</a></code> elements.
- <p>A <dfn id=valid2>valid denominator punctuation character</dfn> is one of
+ <p>A <dfn id=valid3>valid denominator punctuation character</dfn> is one of
the characters from the table below. There is <dfn id=a-value
title="values associated with denominator punctuation characters">a value
associated with each denominator punctuation character</dfn>, as shown in
@@ -3421,7 +3458,7 @@
href="#refsUNICODE">[UNICODE]</a>
<li>If there are still further characters in the string, and the next
- character in the string is a <a href="#valid2">valid denominator
+ character in the string is a <a href="#valid3">valid denominator
punctuation character</a>, set <var title="">denominator</var> to that
character.
@@ -3444,7 +3481,7 @@
sub-algorithm in step 9.
<li>If there are still further characters in the string, and the next
- character in the string is a <a href="#valid2">valid denominator
+ character in the string is a <a href="#valid3">valid denominator
punctuation character</a>, return nothing and abort these steps.
<li>If the string contains any other characters in the range U+0030 DIGIT
@@ -3479,7 +3516,7 @@
<li>Parse <var title="">string</var> according to the <a
href="#rules1">rules for parsing floating point number values</a>, to
obtain <var title="">number</var>. This step cannot fail (<var
- title="">string</var> is guaranteed to be a <a href="#valid1">valid
+ title="">string</var> is guaranteed to be a <a href="#valid2">valid
floating point number</a>).
<li>Return <var title="">number</var>.
@@ -3488,15 +3525,15 @@
<h5 id=percentages-and-dimensions><span class=secno>2.4.3.5.
</span>Percentages and dimensions</h5>
- <p class=big-issue><dfn id=valid3>valid positive non-zero integers</dfn>
+ <p class=big-issue><dfn id=valid4>valid positive non-zero integers</dfn>
<dfn id=rules2>rules for parsing dimension values</dfn> (only used by
height/width on img, embed, object — lengths in css pixels or
percentages)
<h5 id=lists><span class=secno>2.4.3.6. </span>Lists of integers</h5>
- <p>A <dfn id=valid4>valid list of integers</dfn> is a number of <a
- href="#valid0" title="valid integer">valid integers</a> separated by
+ <p>A <dfn id=valid5>valid list of integers</dfn> is a number of <a
+ href="#valid1" title="valid integer">valid integers</a> separated by
U+002C COMMA characters, with no other characters (e.g. no <a
href="#space" title="space character">space characters</a>). In addition,
there might be restrictions on the number of integers that can be given,
@@ -3787,7 +3824,7 @@
<h5 id=specific><span class=secno>2.4.4.1. </span>Specific moments in time</h5>
- <p>A string is a <dfn id=valid5>valid datetime</dfn> if it has four digits
+ <p>A string is a <dfn id=valid6>valid datetime</dfn> if it has four digits
(representing the year), a literal hyphen, two digits (representing the
month), a literal hyphen, two digits (representing the day), optionally
some spaces, either a literal T or a space, optionally some more spaces,
@@ -3820,7 +3857,7 @@
U+002B PLUS SIGN, and the minus U+002D (same as the hyphen).
<div class=example>
- <p>The following are some examples of dates written as <a href="#valid5"
+ <p>The following are some examples of dates written as <a href="#valid6"
title="valid datetime">valid datetimes</a>.</p>
<dl>
@@ -3873,7 +3910,7 @@
user agent must apply the following algorithm to the string. This will
either return a time in UTC, with associated timezone information for
round tripping or display purposes, or nothing, indicating the value is
- not a <a href="#valid5">valid datetime</a>. If at any point the algorithm
+ not a <a href="#valid6">valid datetime</a>. If at any point the algorithm
says that it "fails", this means that it returns nothing.
<ol>
@@ -4485,7 +4522,7 @@
<h4 id=time-offsets><span class=secno>2.4.5 </span>Time offsets</h4>
- <p class=big-issue><dfn id=valid6>valid time offset</dfn>, <dfn
+ <p class=big-issue><dfn id=valid7>valid time offset</dfn>, <dfn
id=rules4>rules for parsing time offsets</dfn>, <dfn id=time-offset>time
offset serialization rules</dfn>; in the format "5d4h3m2s1ms" or "3m 9.2s"
or "00:00:00.00" or similar.
@@ -4682,7 +4719,7 @@
<h4 id=syntax-references><span class=secno>2.4.8 </span>References</h4>
- <p>A <dfn id=valid7>valid hash-name reference</dfn> to an element of type
+ <p>A <dfn id=valid8>valid hash-name reference</dfn> to an element of type
<var title="">type</var> is a string consisting of a U+0023 NUMBER SIGN
(<code title="">#</code>) character followed by a string which exactly
matches the value of the <code title="">name</code> attribute of an
@@ -4778,7 +4815,7 @@
the attribute is absent, then the default value must be returned instead,
or 0 if there is no default value. On setting, the given value must be
converted to the shortest possible string representing the number as a <a
- href="#valid0">valid integer</a> in base ten and then that string must be
+ href="#valid1">valid integer</a> in base ten and then that string must be
used as the new content attribute value.
<p>If a reflecting DOM attribute is an <em>unsigned</em> integer type
@@ -4789,7 +4826,7 @@
hand, it fails, or if the attribute is absent, the default value must be
returned instead, or 0 if there is no default value. On setting, the given
value must be converted to the shortest possible string representing the
- number as a <a href="#valid">valid non-negative integer</a> in base ten
+ number as a <a href="#valid0">valid non-negative integer</a> in base ten
and then that string must be used as the new content attribute value.
<p>If a reflecting DOM attribute is an unsigned integer type
@@ -4804,7 +4841,7 @@
value. On setting, if the value is zero, the user agent must fire an
<code>INDEX_SIZE_ERR</code> exception. Otherwise, the given value must be
converted to the shortest possible string representing the number as a <a
- href="#valid">valid non-negative integer</a> in base ten and then that
+ href="#valid0">valid non-negative integer</a> in base ten and then that
string must be used as the new content attribute value.
<p>If a reflecting DOM attribute is a floating point number type
@@ -4829,7 +4866,7 @@
other hand, it fails, or if the attribute is absent, the default value
must be returned instead, or 0.0 if there is no default value. On setting,
the given value must be converted to the shortest possible string
- representing the number as a <a href="#valid1">valid floating point
+ representing the number as a <a href="#valid2">valid floating point
number</a> in base ten and then that string must be used as the new
content attribute value.
@@ -6160,7 +6197,7 @@
<pre class=idl>interface <dfn id=htmldocument>HTMLDocument</dfn> {
// <a href="#resource0">resource metadata management</a>
[PutForwards=href] readonly attribute <a href="#location2">Location</a> <a href="#location0" title=dom-document-location>location</a>;
- readonly attribute DOMString <a href="#url" title=dom-document-URL>URL</a>;
+ readonly attribute DOMString <a href="#url0" title=dom-document-URL>URL</a>;
attribute DOMString <a href="#domain" title=dom-document-domain>domain</a>;
readonly attribute DOMString <a href="#referrer" title=dom-document-referrer>referrer</a>;
attribute DOMString <a href="#cookie0" title=dom-document-cookie>cookie</a>;
@@ -6229,7 +6266,7 @@
<h4 id=resource><span class=secno>3.2.3 </span><dfn id=resource0>Resource
metadata management</dfn></h4>
- <p>The <dfn id=url title=dom-document-URL><code>URL</code></dfn> attribute
+ <p>The <dfn id=url0 title=dom-document-URL><code>URL</code></dfn> attribute
must return <span>the document's address</span><!--
XXXDOCURL xref -->.
@@ -8532,7 +8569,7 @@
the first are ignored.
<p>The <dfn id=target title=attr-base-target><code>target</code></dfn>
- attribute, if specified, must contain a <a href="#valid9">valid browsing
+ attribute, if specified, must contain a <a href="#valid10">valid browsing
context name or keyword</a>. User agents use this name when <a
href="#following0">following hyperlinks</a>.
@@ -9405,9 +9442,9 @@
attribute must have a value consisting either of:
<ul>
- <li> just a <a href="#valid">valid non-negative integer</a>, or
+ <li> just a <a href="#valid0">valid non-negative integer</a>, or
- <li> a <a href="#valid">valid non-negative integer</a>, followed by a
+ <li> a <a href="#valid0">valid non-negative integer</a>, followed by a
U+003B SEMICOLON (<code title="">;</code>), followed by one or more <a
href="#space" title="space character">space characters</a>, followed by
either a U+0055 LATIN CAPITAL LETTER U or a U+0075 LATIN SMALL LETTER
@@ -11265,7 +11302,7 @@
attribute is omitted, the list is an ascending list (1, 2, 3, ...).
<p>The <dfn id=start0 title=attr-ol-start><code>start</code></dfn>
- attribute, if present, must be a <a href="#valid0">valid integer</a>
+ attribute, if present, must be a <a href="#valid1">valid integer</a>
giving the ordinal value of the first list item.
<p>If the <code title=attr-ol-start><a href="#start0">start</a></code>
@@ -11450,7 +11487,7 @@
element.
<p>The <dfn id=value title=attr-li-value><code>value</code></dfn>
- attribute, if present, must be a <a href="#valid0">valid integer</a>
+ attribute, if present, must be a <a href="#valid1">valid integer</a>
giving the ordinal value of the list item.
<p>If the <code title=attr-li-value><a href="#value">value</a></code>
@@ -12907,7 +12944,7 @@
<p><strong>Author requirements</strong>: The <code
title=attr-progress-max><a href="#max">max</a></code> and <code
title=attr-progress-value><a href="#value1">value</a></code> attributes,
- when present, must have values that are <a href="#valid1" title="valid
+ when present, must have values that are <a href="#valid2" title="valid
floating point number">valid floating point numbers</a>. The <code
title=attr-progress-max><a href="#max">max</a></code> attribute, if
present, must have a value greater than zero. The <code
@@ -13122,7 +13159,7 @@
title=attr-meter-max><a href="#max1">max</a></code>, and <code
title=attr-meter-optimum><a href="#optimum">optimum</a></code> attributes
are all optional. When present, they must have values that are <a
- href="#valid1" title="valid floating point number">valid floating point
+ href="#valid2" title="valid floating point number">valid floating point
numbers</a>, and their values must satisfy the following inequalities:
<ul class=brief>
@@ -14385,14 +14422,14 @@
<p>If present, the <code title=attr-mod-datetime><a
href="#datetime1">datetime</a></code> attribute must be a <a
- href="#valid5">valid datetime</a> value.
+ href="#valid6">valid datetime</a> value.
<p>User agents must parse the <code title=attr-mod-datetime><a
href="#datetime1">datetime</a></code> attribute according to the <a
href="#datetime-parser">parse a string as a datetime value</a> algorithm.
If that doesn't return a time, then the modification has no associated
timestamp (the value is non-conforming; it is not a <a
- href="#valid5">valid datetime</a>). Otherwise, the modification is marked
+ href="#valid6">valid datetime</a>). Otherwise, the modification is marked
as having been made at the given datetime. User agents should use the
associated timezone information to determine which timezone to present the
given datetime in.
@@ -15405,7 +15442,7 @@
will remain at the initial <code>about:blank</code><!-- XXX xref --> page.
<p>The <dfn id=name1 title=attr-iframe-name><code>name</code></dfn>
- attribute, if present, must be a <a href="#valid8">valid browsing context
+ attribute, if present, must be a <a href="#valid9">valid browsing context
name</a>. When the browsing context is created, if the attribute is
present, the <a href="#browsing2">browsing context name</a> must be set to
the value of this attribute; otherwise, the <a href="#browsing2">browsing
@@ -15964,7 +16001,7 @@
href="#type6">type</a></code> attributes must be present.
<p>The <dfn id=name3 title=attr-object-name><code>name</code></dfn>
- attribute, if present, must be a <a href="#valid8">valid browsing context
+ attribute, if present, must be a <a href="#valid9">valid browsing context
name</a>.
<p>When the element is created, and subsequently whenever the <code
@@ -16909,7 +16946,7 @@
allows the author to specify the pixel ratio of anamorphic <a
href="#media10" title="media resource">media resources</a> that do not
self-describe their pixel ratio. The attribute value, if specified, must
- be a <a href="#valid1">valid floating point number</a> giving the ratio of
+ be a <a href="#valid2">valid floating point number</a> giving the ratio of
the correct rendered width of each pixel to the actual width of each pixel
in the image (i.e., the multiple by which the video's intrinsic width is
to be multiplied to obtain the rendered width that gives the correct
@@ -19295,7 +19332,7 @@
to control the size of the coordinate space: <dfn id=width0
title=attr-canvas-width><code>width</code></dfn> and <dfn id=height0
title=attr-canvas-height><code>height</code></dfn>. These attributes, when
- specified, must have values that are <a href="#valid" title="valid
+ specified, must have values that are <a href="#valid0" title="valid
non-negative integer">valid non-negative integers</a>. The <a
href="#rules">rules for parsing non-negative integers</a> must be used to
obtain their numeric values. If an attribute is missing, or if parsing its
@@ -20722,9 +20759,8 @@
href="#globalcompositeoperation"
title=dom-context-2d-globalCompositeOperation>global composition
operators</a>. (Transformations affect the path when the path is created,
- not when it is painted, though the stroke <em><a
- href="#style1">style</a></em> is still affected by the transformation
- during painting.)
+ not when it is painted, though the stroke <em title="">style</em> is still
+ affected by the transformation during painting.)
<p>Zero-length line segments must be pruned before stroking a path. Empty
subpaths must be ignored.
@@ -22060,7 +22096,7 @@
href="#rectangle" title=attr-area-shape-rect>rectangle</a> state.
<p>The <dfn id=coords title=attr-area-coords><code>coords</code></dfn>
- attribute must, if specified, contain a <a href="#valid4">valid list of
+ attribute must, if specified, contain a <a href="#valid5">valid list of
integers</a>. This attribute gives the coordinates for the shape described
by the <code title=attr-area-shape><a href="#shape">shape</a></code>
attribute. The processing for this attribute is described as part of the
@@ -22190,7 +22226,7 @@
<code><a href="#img">img</a></code> or <code><a
href="#object">object</a></code> element. The <code
title=attr-area-usemap>usemap</code> attribute, if specified, must be a <a
- href="#valid7">valid hash-name reference</a> to a <code><a
+ href="#valid8">valid hash-name reference</a> to a <code><a
href="#map">map</a></code> element.
<p>If an <code><a href="#img">img</a></code> element or an <code><a
@@ -22512,7 +22548,7 @@
give the dimensions of the visual content of the element (the width and
height respectively, relative to the nominal direction of the output
medium), in CSS pixels. The attributes, if specified, must have values
- that are <a href="#valid3">valid positive non-zero integers</a>.
+ that are <a href="#valid4">valid positive non-zero integers</a>.
<p>The specified dimensions given may differ from the dimensions specified
in the resource itself, since the resource may have a resolution that
@@ -22925,7 +22961,7 @@
<p>If the <code><a href="#colgroup">colgroup</a></code> element contains no
<code><a href="#col">col</a></code> elements, then the element may have a
<dfn id=span0 title=attr-colgroup-span><code>span</code></dfn> content
- attribute specified, whose value must be a <a href="#valid">valid
+ attribute specified, whose value must be a <a href="#valid0">valid
non-negative integer</a> greater than zero.
<p>The <code><a href="#colgroup">colgroup</a></code> element and its <code
@@ -22979,7 +23015,7 @@
<p>The element may have a <dfn id=span2
title=attr-col-span><code>span</code></dfn> content attribute specified,
- whose value must be a <a href="#valid">valid non-negative integer</a>
+ whose value must be a <a href="#valid0">valid non-negative integer</a>
greater than zero.
<p>The <code><a href="#col">col</a></code> element and its <code
@@ -23452,13 +23488,13 @@
<p>The <code><a href="#td">td</a></code> and <code><a
href="#th">th</a></code> elements may have a <dfn id=colspan
title=attr-tdth-colspan><code>colspan</code></dfn> content attribute
- specified, whose value must be a <a href="#valid">valid non-negative
+ specified, whose value must be a <a href="#valid0">valid non-negative
integer</a> greater than zero.
<p>The <code><a href="#td">td</a></code> and <code><a
href="#th">th</a></code> elements may also have a <dfn id=rowspan
title=attr-tdth-rowspan><code>rowspan</code></dfn> content attribute
- specified, whose value must be a <a href="#valid">valid non-negative
+ specified, whose value must be a <a href="#valid0">valid non-negative
integer</a>.
<p>The <code><a href="#td">td</a></code> and <code><a
@@ -24898,7 +24934,7 @@
agents must use all the child nodes of the <code><a
href="#script1">script</a></code> element as the script to execute.</p>
</dl>
-
+ <!-- SCRIPT EXEC -->
<p>In any case, the user agent must execute the script according to the
semantics defined by the language associated with <var><a
href="#the-scripts">the script's type</a></var> (see the <a
@@ -24908,6 +24944,10 @@
must be the <code><a href="#window">Window</a></code> object of that
<a href="#browsing1">browsing context</a>.</p>
+ <p>The <a href="#script4">script document context</a> of the script
+ must be the <code>Document</code> object that owns the <code><a
+ href="#script1">script</a></code> element.</p>
+
<p class=note>The element's attributes' values might have changed
between when the element was inserted into the document and when the
script has finished loading, as may its other attributes; similarly,
@@ -29687,12 +29727,12 @@
name</dfn>. By default, a browsing context has no name (its name is not
set).
- <p>A <dfn id=valid8>valid browsing context name</dfn> is any string with at
+ <p>A <dfn id=valid9>valid browsing context name</dfn> is any string with at
least one character that does not start with a U+005F LOW LINE character.
(Names starting with an underscore are reserved for special keywords.)
- <p>A <dfn id=valid9>valid browsing context name or keyword</dfn> is any
- string that is either a <a href="#valid8">valid browsing context name</a>
+ <p>A <dfn id=valid10>valid browsing context name or keyword</dfn> is any
+ string that is either a <a href="#valid9">valid browsing context name</a>
or that case-insensitively <!-- ASCII --> matches one of: <code
title="">_blank</code>, <code title="">_self</code>, <code
title="">_parent</code>, or <code title="">_top</code>.
@@ -29992,7 +30032,7 @@
<p>The second argument, <var title="">target</var>, specifies the <a
href="#browsing2" title="browsing context name">name</a> of the browsing
- context that is to be navigated. It must be a <a href="#valid9">valid
+ context that is to be navigated. It must be a <a href="#valid10">valid
browsing context name or keyword</a>. If fewer than two arguments are
provided, then the <var title="">name</var> argument defaults to the value
"<code>_blank</code>".
@@ -30035,16 +30075,9 @@
href="#browsing1">browsing context</a> was just created as part of the <a
href="#the-rules">the rules for choosing a browsing context given a
browsing context name</a>. The navigation must be done with the <a
- href="#browsing1">browsing context</a> corresponding to the <code><a
- href="#window">Window</a></code> object that is the <a
- href="#script2">script execution context</a> of the script that invoked
- the method as the <a href="#source0">source browsing context</a>.
+ href="#script3">script browsing context</a> of the script that invoked the
+ method as the <a href="#source0">source browsing context</a>.
- <p class=note>If the <a href="#script2">script execution context</a> of a
- script isn't a <code><a href="#window">Window</a></code> object, then it
- can't ever get to a <code><a href="#window">Window</a></code> object to
- call this method.
-
<p>The method must return the <code><a href="#window">Window</a></code>
object of the default view of the <a href="#browsing1">browsing
context</a> that was navigated, or null if no browsing context was
@@ -30174,6 +30207,12 @@
<dd>The owner is the <code>Document</code> to which the <code><a
href="#script1">script</a></code> element belongs.
+ <dt>If a script is in an <a href="#event3" title="event handler content
+ attributes">event handler content attribute</a>
+
+ <dd>The owner is the <code>Document</code> to which the attribute node
+ belongs.
+
<dt>If a script is a function or other code reference created by another
script
@@ -30508,20 +30547,35 @@
scripting features.
</ul>
+ <p>When a script is created<!-- which is marked by SCRIPT EXEC in
+ this spec -->,
+ it is associated with a <a href="#script2">script execution context</a>, a
+ <a href="#script3">script browsing context</a>, and a <a
+ href="#script4">script document context</a>.</p>
+ <!-- SCRIPT EXEC -->
+
<h4 id=script0><span class=secno>5.4.1 </span>Script execution contexts</h4>
<p>The <dfn id=script2>script execution context</dfn> of a script is
- defined when that script is created. It is typically a <code><a
- href="#window">Window</a></code> object.
+ defined when that script is created. It is either a <code><a
+ href="#window">Window</a></code> object or an empty object.
+ <p>When the <a href="#script2">script execution context</a> of a script is
+ an empty object, it can't do anything that interacts with the environment.
+
+ <hr>
+
<p>A <a href="#script2">script execution context</a> always has an
- associated <a href="#browsing1">browsing context</a>. If the <a
- href="#script2">script execution context</a> is a <code><a
- href="#window">Window</a></code> object, then that object's <a
- href="#browsing1">browsing context</a> is it. Otherwise, the <a
- href="#script2">script execution context</a> is associated explicitly with
- a <a href="#browsing1">browsing context</a> when it is created.
+ associated <a href="#browsing1">browsing context</a>, known as the <dfn
+ id=script3>script browsing context</dfn>. If the <a href="#script2">script
+ execution context</a> is a <code><a href="#window">Window</a></code>
+ object, then that object's <a href="#browsing1">browsing context</a> is
+ it. Otherwise, the <a href="#script2">script execution context</a> is
+ associated explicitly with a <a href="#browsing1">browsing context</a>
+ when it is created.
+ <hr>
+
<p>It is said that <dfn id=scripting1>scripting is disabled</dfn> in a <a
href="#script2">script execution context</a> when any of the following
conditions are true:
@@ -30548,8 +30602,8 @@
</ul>
<p>A node is said to be <dfn id=without>without script</dfn> if either the
- <code>Document</code> object of the node (the node itself, it is itself a
- <code>Document</code> object) does not have an associated <a
+ <code>Document</code> object of the node (the node itself, if it is itself
+ a <code>Document</code> object) does not have an associated <a
href="#browsing1">browsing context</a>, or <a href="#scripting1">scripting
is disabled</a> in that <a href="#browsing1">browsing context</a>.
@@ -30569,9 +30623,19 @@
will disable any event handler attributes, event listeners, timeouts, etc,
that were set by scripts in the document.
+ <hr>
+
+ <p>Every script whose <a href="#script2">script execution context</a> is a
+ <code><a href="#window">Window</a></code> object is also associated with a
+ <code>Document</code> object, known as its <dfn id=script4>script document
+ context</dfn>. It is used to resolve URLs. The document is assigned when
+ the script is created, as with the <a href="#script3">script browsing
+ context</a>.
+
<h4 id=security4><span class=secno>5.4.2 </span>Security exceptions</h4>
- <p class=big-issue>Define <dfn id=security9>security exception</dfn>.
+ <p class=big-issue>Define <dfn id=security9>security exception</dfn>.</p>
+ <!-- SCRIPT EXEC -->
<h4 id=javascript-protocol><span class=secno>5.4.3 </span><dfn
id=the-javascript title="javascript protocol">The <code
@@ -30597,7 +30661,9 @@
href="#same-origin">same origin</a> as the script given by that URI, the
<a href="#script2">script execution context</a> must be the <code><a
href="#window">Window</a></code> object of the <a
- href="#browsing1">browsing context</a> being navigated.</p>
+ href="#browsing1">browsing context</a> being navigated, and the <a
+ href="#script4">script document context</a> must be that <a
+ href="#active">active document</a>.</p>
<!-- XXXURL JSURL issue -->
<p>When a browsing context is <a href="#navigate"
@@ -30606,8 +30672,7 @@
href="#origin0">origin</a> that is <em>not</em> the <a href="#same-origin"
title="same origin">same</a> as that of the script given by the URI, the
<a href="#script2">script execution context</a> must be an empty object,
- and the <a href="#script2">script execution context</a>'s associated <a
- href="#browsing1">browsing context</a> must be the <a
+ and the <a href="#script3">script browsing context</a> must be the <a
href="#browsing1">browsing context</a> being <a href="#navigate"
title=navigate>navigated</a>.</p>
<!-- XXXURL JSURL issue -->
@@ -30697,7 +30762,8 @@
<p><dfn id=event3>Event handler content attributes</dfn>, when specified,
must contain valid ECMAScript code matching the ECMAScript <code
title="">FunctionBody</code> production. <a
- href="#refsECMA262">[ECMA262]</a>
+ href="#refsECMA262">[ECMA262]</a></p>
+ <!-- SCRIPT EXEC -->
<p>When an event handler content attribute is set, its new value must be
interpreted as the body of an anonymous function with a single argument
@@ -30720,7 +30786,9 @@
<p>The <a href="#script2">script execution context</a> of the event handler
must be the <code><a href="#window">Window</a></code> object at the end of
- the scope chain.
+ the scope chain. The <a href="#script4">script document context</a> of the
+ event handler must be the <code>Document</code> object that owns the event
+ handler content attribute that was set.
<p class=big-issue>How do we allow non-JS event handlers?
@@ -31402,16 +31470,10 @@
<li>
<p><a href="#navigate">Navigate</a> the new browsing context to <var
title="">url</var>, with <a href="#replacement">replacement enabled</a>,
- and with the <a href="#browsing1">browsing context</a> of the <code><a
- href="#window">Window</a></code> object that is the <a
- href="#script2">script execution context</a> of the script that invoked
- the method as the <a href="#source0">source browsing context</a>.</p>
+ and with the <a href="#script3">script browsing context</a> of the
+ script that invoked the method as the <a href="#source0">source browsing
+ context</a>.</p>
- <p class=note>If the <a href="#script2">script execution context</a> of a
- script isn't a <code><a href="#window">Window</a></code> object, then it
- can't ever get to a <code><a href="#window">Window</a></code> object to
- call this method.</p>
-
<li>
<p>Wait for the browsing context to be closed. (The user agent must allow
the user to indicate that the browsing context is to be closed.)</p>
@@ -31505,22 +31567,19 @@
method, when invoked, must cause the user agent to show a notification.
<p id=sandboxNotifications>If the method was invoked from a script whose <a
- href="#script2">script execution context</a>'s associated <a
- href="#browsing1">browsing context</a> has the <a
+ href="#script3">script browsing context</a> has the <a
href="#sandboxed1">sandboxed annoyances browsing context flag</a> set,
then the notification must be shown within that <a
href="#browsing1">browsing context</a>. The notification is said to be a
<dfn id=sandboxed5>sandboxed notification</dfn>.
<p>Otherwise, if the <a href="#origin0">origin</a> of the <a
- href="#browsing1">browsing context</a> associated with the <a
- href="#script2">script execution context</a> of the script that invoked
- the method is <em>not</em> flagged as being a <a href="#trusted">trusted
+ href="#script3">script browsing context</a> of the script that invoked the
+ method is <em>not</em> flagged as being a <a href="#trusted">trusted
notification source</a>, then the notification should be rendered within
the <a href="#top-level">top-level browsing context</a> of the <a
- href="#browsing1">browsing context</a> associated with the <a
- href="#script2">script execution context</a> of the script that invoked
- the method. The notification is said to be a <dfn id=normal>normal
+ href="#script3">script browsing context</a> of the script that invoked the
+ method. The notification is said to be a <dfn id=normal>normal
notification</dfn>. User agents should provide a way to set the origin's
<a href="#trusted">trusted notification source</a> flag from the
notification, so that the user can benefit from notifications even when
@@ -31564,16 +31623,14 @@
<p>When a <a href="#normal">normal notification</a> (but not a <a
href="#sandboxed5">sandboxed notification</a>) is shown, the user agent
may bring the user's attention to the <a href="#top-level">top-level
- browsing context</a> of the <a href="#browsing1">browsing context</a>
- associated with the <a href="#script2">script execution context</a> of the
- script that invoked the method, if that would be useful; but user agents
- should not use system-wide notification mechanisms to do so.
+ browsing context</a> of the <a href="#script3">script browsing context</a>
+ of the script that invoked the method, if that would be useful; but user
+ agents should not use system-wide notification mechanisms to do so.
<p>When a <a href="#trusted0">trusted notification</a> is shown, the user
agent should bring the user's attention to the notification and the <a
- href="#browsing1">browsing context</a> associated with the <a
- href="#script2">script execution context</a> of the script that invoked
- the method, as per the platform conventions for attracting the user's
+ href="#script3">script browsing context</a> of the script that invoked the
+ method, as per the platform conventions for attracting the user's
attention to applications.
<div class=example>
@@ -31599,8 +31656,7 @@
title=meta-application-name>application name</a>, if available, or else
the <a href="#document.title" title=dom-document-title>document
title</a>, of the <a href="#active">active document</a> of the <a
- href="#browsing1">browsing context</a> associated with the <a
- href="#script2">script execution context</a> of the script that invoked
+ href="#script3">script browsing context</a> of the script that invoked
the method.
<li>An icon chosen from the <a href="#links1" title="external resource
@@ -31640,8 +31696,7 @@
<p>User agents should support user interaction with notifications, if and
as appropriate given the platform conventions. If a user activates a
notification, and the <var title="">onclick</var> callback argument was
- present and is not null, then the <a href="#browsing1">browsing
- context</a> associated with the <a href="#script2">script execution
+ present and is not null, then the <a href="#script3">script browsing
context</a> of the function given by <var title="">onclick</var> should be
brought to the user's attention, and the <var title="">onclick</var>
callback should then be invoked.
@@ -33907,15 +33962,8 @@
<p>Navigation for the <code title=dom-location-assign><a
href="#assign">assign()</a></code> and <code title=dom-location-replace><a
href="#replace">replace()</a></code> methods must be done with the <a
- href="#browsing1">browsing context</a> of the <code><a
- href="#window">Window</a></code> object that is the <a
- href="#script2">script execution context</a> of the script that invoked
- the method as the <a href="#source0">source browsing context</a>.
-
- <p class=note>If the <a href="#script2">script execution context</a> of a
- script isn't a <code><a href="#window">Window</a></code> object, then it
- can't ever get to a <code><a href="#location2">Location</a></code> object
- to call these methods.</p>
+ href="#script3">script browsing context</a> of the script that invoked the
+ method as the <a href="#source0">source browsing context</a>.</p>
<!-- XXXURL algorithms -->
<p>Relative <var title="">url</var> arguments for <code
@@ -35996,7 +36044,7 @@
<p>The <dfn id=target3
title=attr-hyperlink-target><code>target</code></dfn> attribute, if
- present, must be a <a href="#valid9">valid browsing context name or
+ present, must be a <a href="#valid10">valid browsing context name or
keyword</a>. User agents use this name when <a
href="#following0">following hyperlinks</a>.</p>
<!-- XXXURL change to URL -->
@@ -36853,7 +36901,7 @@
href="#unordered">unordered set of unique space-separated tokens</a>. The
values must all be either <code title=attr-link-sizes-any><a
href="#any">any</a></code> or a value that consists of two <a
- href="#valid" title="valid non-negative integer">valid non-negative
+ href="#valid0" title="valid non-negative integer">valid non-negative
integers</a> that do not have a leading U+0030 DIGIT ZERO (0) character
and that are separated by a single U+0078 LATIN SMALL LETTER X character.
@@ -37628,7 +37676,7 @@
<p>The <code title=attr-tabindex><a href="#tabindex">tabindex</a></code>
attribute, if specified, must have a value that is a <a
- href="#valid0">valid integer</a>.
+ href="#valid1">valid integer</a>.
<p>If the attribute is specified, it must be parsed using the <a
href="#rules0">rules for parsing integers</a>. The attribute's values have
Modified: source
===================================================================
--- source 2008-06-19 09:27:25 UTC (rev 1790)
+++ source 2008-06-24 00:21:03 UTC (rev 1791)
@@ -945,6 +945,39 @@
<h3>URLs</h3><!-- XXXURL -->
+ <p class="big-issue">The text in this section is not yet integrated
+ with the rest of the specification.</p>
+
+ <h4>Terminology</h4>
+
+ <p>A <dfn>URL</dfn> is a string used to identify a resource. A
+ <span>URL</span> is always associated with a <code>Document</code>,
+ either explicitly when the URL is created or defined; or through a
+ DOM node, in which case the associated <code>Document</code> is the
+ node's <code>Document</code>; or through a script, in which case the
+ associated <code>Document</code> is the script's <span>script
+ document context</span>.</p>
+
+ <p>A <span>URL</span> is a <dfn>valid URL</dfn> if at least one of
+ the following conditions holds:</p>
+
+ <ul>
+
+ <li><p>The <span>URL</span> is a valid URI.</p></li>
+
+ <li><p>The <span>URL</span> is a valid IRI and it has no query
+ component.</p></li>
+
+ <li><p>The <span>URL</span> is a valid IRI and its query component
+ contains no unescaped non-ASCII characters.</p></li>
+
+ <li><p>The <span>URL</span> is a valid IRI and the <span
+ title="document's character encoding">character encoding</span> of
+ the URL's <code>Document</code> is UTF-8.</p></li>
+
+ </ul>
+
+
<div class="big-issue">
<p>This section will do the following:</p>
@@ -18203,8 +18236,9 @@
title="clipping region">clipping region</span>, and <span
title="dom-context-2d-globalCompositeOperation">global composition
operators</span>. (Transformations affect the path when the path is
- created, not when it is painted, though the stroke <em>style</em> is
- still affected by the transformation during painting.)</p>
+ created, not when it is painted, though the stroke <em
+ title="">style</em> is still affected by the transformation during
+ painting.)</p>
<p>Zero-length line segments must be pruned before stroking a
path. Empty subpaths must be ignored.</p>
@@ -22584,6 +22618,7 @@
</dl>
+ <!-- SCRIPT EXEC -->
<p>In any case, the user agent must execute the script according to
the semantics defined by the language associated with <var>the
script's type</var> (see the <a href="#scriptingLanguages">scripting
@@ -22593,6 +22628,10 @@
be the <code>Window</code> object of that <span>browsing
context</span>.</p>
+ <p>The <span>script document context</span> of the script must
+ be the <code>Document</code> object that owns the
+ <code>script</code> element.</p>
+
<p class="note">The element's attributes' values might have changed
between when the element was inserted into the document and when the
script has finished loading, as may its other attributes; similarly,
@@ -27526,15 +27565,9 @@
<span>browsing context</span> was just created as part of the
<span>the rules for choosing a browsing context given a browsing
context name</span>. The navigation must be done with the
- <span>browsing context</span> corresponding to the
- <code>Window</code> object that is the <span>script execution
- context</span> of the script that invoked the method as the
- <span>source browsing context</span>.</p>
+ <span>script browsing context</span> of the script that invoked the
+ method as the <span>source browsing context</span>.</p>
- <p class="note">If the <span>script execution context</span> of a
- script isn't a <code>Window</code> object, then it can't ever get to
- a <code>Window</code> object to call this method.</p>
-
<p>The method must return the <code>Window</code> object of the
default view of the <span>browsing context</span> that was
navigated, or null if no browsing context was navigated.</p>
@@ -27665,6 +27698,12 @@
<code>script</code> element belongs.</dd>
+ <dt>If a script is in an <span title="event handler content attributes">event handler content attribute</span></dt>
+
+ <dd>The owner is the <code>Document</code> to which the
+ attribute node belongs.</dd>
+
+
<dt>If a script is a function or other code reference created by
another script</dt>
@@ -28057,21 +28096,36 @@
</ul>
+ <p>When a script is created<!-- which is marked by SCRIPT EXEC in
+ this spec -->, it is associated with a <span>script execution
+ context</span>, a <span>script browsing context</span>, and a
+ <span>script document context</span>.</p>
+
+ <!-- SCRIPT EXEC -->
<h4>Script execution contexts</h4>
<p>The <dfn>script execution context</dfn> of a script is defined
- when that script is created. It is typically a <code>Window</code>
- object.</p>
+ when that script is created. It is either a <code>Window</code>
+ object or an empty object.</p>
+ <p>When the <span>script execution context</span> of a script is an
+ empty object, it can't do anything that interacts with the
+ environment.</p>
+
+ <hr>
+
<p>A <span>script execution context</span> always has an associated
- <span>browsing context</span>. If the <span>script execution
- context</span> is a <code>Window</code> object, then that object's
- <span>browsing context</span> is it. Otherwise, the <span>script
- execution context</span> is associated explicitly with a
- <span>browsing context</span> when it is created.</p>
+ <span>browsing context</span>, known as the <dfn>script browsing
+ context</dfn>. If the <span>script execution context</span> is a
+ <code>Window</code> object, then that object's <span>browsing
+ context</span> is it. Otherwise, the <span>script execution
+ context</span> is associated explicitly with a <span>browsing
+ context</span> when it is created.</p>
+ <hr>
+
<p>It is said that <dfn>scripting is disabled</dfn> in a
<span>script execution context</span> when any of the following
conditions are true:</p>
@@ -28098,7 +28152,7 @@
</ul>
<p>A node is said to be <dfn>without script</dfn> if either the
- <code>Document</code> object of the node (the node itself, it is
+ <code>Document</code> object of the node (the node itself, if it is
itself a <code>Document</code> object) does not have an associated
<span>browsing context</span>, or <span>scripting is disabled</span>
in that <span>browsing context</span>.</p>
@@ -28119,13 +28173,22 @@
event handler attributes, event listeners, timeouts, etc, that were
set by scripts in the document.</p>
+ <hr>
+ <p>Every script whose <span>script execution context</span> is a
+ <code>Window</code> object is also associated with a
+ <code>Document</code> object, known as its <dfn>script document
+ context</dfn>. It is used to resolve URLs. The document is assigned
+ when the script is created, as with the <span>script browsing
+ context</span>.</p>
+
<h4>Security exceptions</h4>
<p class="big-issue">Define <dfn>security exception</dfn>.</p>
+ <!-- SCRIPT EXEC -->
<h4 id="javascript-protocol"><dfn title="javascript protocol">The <code title="">javascript:</code> protocol</dfn></h4>
<!-- XXXURL merge into URLs section? (we could define 'fetch'/'download' while we're at it?) -->
@@ -28150,7 +28213,8 @@
the <span>same origin</span> as the script given by that URI, the
<span>script execution context</span> must be the
<code>Window</code> object of the <span>browsing context</span>
- being navigated.</p>
+ being navigated, and the <span>script document context</span> must
+ be that <span>active document</span>.</p>
<!-- XXXURL JSURL issue -->
<p>When a browsing context is <span
@@ -28159,8 +28223,7 @@
<span>origin</span> that is <em>not</em> the <span title="same
origin">same</span> as that of the script given by the URI, the
<span>script execution context</span> must be an empty object, and
- the <span>script execution context</span>'s associated
- <span>browsing context</span> must be the <span>browsing
+ the <span>script browsing context</span> must be the <span>browsing
context</span> being <span title="navigate">navigated</span>.</p>
<!-- XXXURL JSURL issue -->
@@ -28253,6 +28316,7 @@
title="">FunctionBody</code> production. <a
href="#refsECMA262">[ECMA262]</a></p>
+ <!-- SCRIPT EXEC -->
<p>When an event handler content attribute is set, its new value
must be interpreted as the body of an anonymous function with a
single argument called <code>event</code>, with the new function's
@@ -28275,7 +28339,9 @@
<p>The <span>script execution context</span> of the event handler
must be the <code>Window</code> object at the end of the scope
- chain.</p>
+ chain. The <span>script document context</span> of the event handler
+ must be the <code>Document</code> object that owns the event handler
+ content attribute that was set.</p>
<p class="big-issue">How do we allow non-JS event handlers?</p>
@@ -28956,15 +29022,10 @@
<p><span>Navigate</span> the new browsing context to <var
title="">url</var>, with <span>replacement enabled</span>, and
- with the <span>browsing context</span> of the <code>Window</code>
- object that is the <span>script execution context</span> of the
- script that invoked the method as the <span>source browsing
+ with the <span>script browsing context</span> of the script that
+ invoked the method as the <span>source browsing
context</span>.</p>
- <p class="note">If the <span>script execution context</span> of a
- script isn't a <code>Window</code> object, then it can't ever get
- to a <code>Window</code> object to call this method.</p>
-
</li>
<li>
@@ -29073,24 +29134,22 @@
cause the user agent to show a notification.</p>
<p id="sandboxNotifications">If the method was invoked from a script
- whose <span>script execution context</span>'s associated
- <span>browsing context</span> has the <span>sandboxed annoyances
- browsing context flag</span> set, then the notification must be
- shown within that <span>browsing context</span>. The notification is
- said to be a <dfn>sandboxed notification</dfn>.</p>
+ whose <span>script browsing context</span> has the <span>sandboxed
+ annoyances browsing context flag</span> set, then the notification
+ must be shown within that <span>browsing context</span>. The
+ notification is said to be a <dfn>sandboxed notification</dfn>.</p>
- <p>Otherwise, if the <span>origin</span> of the <span>browsing
- context</span> associated with the <span>script execution
- context</span> of the script that invoked the method is <em>not</em>
- flagged as being a <span>trusted notification source</span>, then
- the notification should be rendered within the <span>top-level
- browsing context</span> of the <span>browsing context</span>
- associated with the <span>script execution context</span> of the
- script that invoked the method. The notification is said to be a
- <dfn>normal notification</dfn>. User agents should provide a way to
- set the origin's <span>trusted notification source</span> flag from
- the notification, so that the user can benefit from notifications
- even when the user agent is not the active application.</p>
+ <p>Otherwise, if the <span>origin</span> of the <span>script
+ browsing context</span> of the script that invoked the method is
+ <em>not</em> flagged as being a <span>trusted notification
+ source</span>, then the notification should be rendered within the
+ <span>top-level browsing context</span> of the <span>script browsing
+ context</span> of the script that invoked the method. The
+ notification is said to be a <dfn>normal notification</dfn>. User
+ agents should provide a way to set the origin's <span>trusted
+ notification source</span> flag from the notification, so that the
+ user can benefit from notifications even when the user agent is not
+ the active application.</p>
<p>Otherwise, the <span>origin</span> is flagged as a <span>trusted
notification source</span>, and the notification should be shown
@@ -29134,17 +29193,16 @@
<p>When a <span>normal notification</span> (but not a
<span>sandboxed notification</span>) is shown, the user agent may
bring the user's attention to the <span>top-level browsing
- context</span> of the <span>browsing context</span> associated with
- the <span>script execution context</span> of the script that invoked
- the method, if that would be useful; but user agents should not use
- system-wide notification mechanisms to do so.</p>
+ context</span> of the <span>script browsing context</span> of the
+ script that invoked the method, if that would be useful; but user
+ agents should not use system-wide notification mechanisms to do
+ so.</p>
<p>When a <span>trusted notification</span> is shown, the user agent
should bring the user's attention to the notification and the
- <span>browsing context</span> associated with the <span>script
- execution context</span> of the script that invoked the method, as
- per the platform conventions for attracting the user's attention to
- applications.</p>
+ <span>script browsing context</span> of the script that invoked the
+ method, as per the platform conventions for attracting the user's
+ attention to applications.</p>
<div class="example">
@@ -29171,9 +29229,8 @@
<li>The <span title="meta-application-name">application
name</span>, if available, or else the <span
title="dom-document-title">document title</span>, of the
- <span>active document</span> of the <span>browsing context</span>
- associated with the <span>script execution context</span> of the
- script that invoked the method.</li>
+ <span>active document</span> of the <span>script browsing
+ context</span> of the script that invoked the method.</li>
<li>An icon chosen from the <span title="external resource
link">external resource links</span> of type <code
@@ -29216,9 +29273,8 @@
<p>User agents should support user interaction with notifications,
if and as appropriate given the platform conventions. If a user
activates a notification, and the <var title="">onclick</var>
- callback argument was present and is not null, then the
- <span>browsing context</span> associated with the <span>script
- execution context</span> of the function given by <var
+ callback argument was present and is not null, then the <span>script
+ browsing context</span> of the function given by <var
title="">onclick</var> should be brought to the user's attention,
and the <var title="">onclick</var> callback should then be
invoked.</p>
@@ -31542,15 +31598,9 @@
<p>Navigation for the <code
title="dom-location-assign">assign()</code> and <code
title="dom-location-replace">replace()</code> methods must be done
- with the <span>browsing context</span> of the <code>Window</code>
- object that is the <span>script execution context</span> of the
- script that invoked the method as the <span>source browsing
- context</span>.</p>
+ with the <span>script browsing context</span> of the script that
+ invoked the method as the <span>source browsing context</span>.</p>
- <p class="note">If the <span>script execution context</span> of a
- script isn't a <code>Window</code> object, then it can't ever get to
- a <code>Location</code> object to call these methods.</p>
-
<!-- XXXURL algorithms -->
<p>Relative <var title="">url</var> arguments for <code
title="dom-location-assign">assign()</code> and <code
More information about the Commit-Watchers
mailing list