[html5] r2468 - [] (0) Define 'the document's address'.
whatwg at whatwg.org
whatwg at whatwg.org
Wed Nov 26 18:00:32 PST 2008
Author: ianh
Date: 2008-11-26 18:00:31 -0800 (Wed, 26 Nov 2008)
New Revision: 2468
Modified:
index
source
Log:
[] (0) Define 'the document's address'.
Modified: index
===================================================================
--- index 2008-11-26 23:14:05 UTC (rev 2467)
+++ index 2008-11-27 02:00:31 UTC (rev 2468)
@@ -17,7 +17,7 @@
<div class=head>
<p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<h1>HTML 5</h1>
- <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 26 November 2008</h2>
+ <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 27 November 2008</h2>
<p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<dl><dt>Multiple-page version:</dt>
@@ -3954,20 +3954,20 @@
<ol><li><p>If there is no <code><a href=#the-base-element>base</a></code> element that is both a
child of <a href=#the-head-element-0>the <code>head</code> element</a> and has an
<code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute, then the
- <a href=#document-base-url>document base URL</a> is <span>the document's
- address</span><!-- XXXDOCURL -->.</li>
+ <a href=#document-base-url>document base URL</a> is <a href="#the-document's-address">the document's
+ address</a>.</li>
<li><p>Otherwise, let <var title="">url</var> be the value of the
<code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute of the first such
element.</li>
- <li><p><a href=#resolve-a-url title="resolve a URL">Resolve</a> the <var title="">url</var> URL, using <span>the document's
- address</span><!-- XXXDOCURL --> as the <a href=#base-url>base URL</a>
- (thus, the <code><a href=#the-base-element>base</a></code> <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute isn't affect by <code title=attr-xml-base><a href=#the-xml:base-attribute-(xml-only)>xml:base</a></code> attributes).</li>
+ <li><p><a href=#resolve-a-url title="resolve a URL">Resolve</a> the <var title="">url</var> URL, using <a href="#the-document's-address">the document's address</a>
+ as the <a href=#base-url>base URL</a> (thus, the <code><a href=#the-base-element>base</a></code> <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute isn't affected by
+ <code title=attr-xml-base><a href=#the-xml:base-attribute-(xml-only)>xml:base</a></code> attributes).</li>
<li><p>The <a href=#document-base-url>document base URL</a> is the result of the
- previous step if it was successful; otherwise it is <span>the
- document's address</span><!-- XXXDOCURL -->.</li>
+ previous step if it was successful; otherwise it is <a href="#the-document's-address">the
+ document's address</a>.</li>
</ol><p>To <dfn id=resolve-a-url>resolve a URL</dfn> to an <a href=#absolute-url>absolute URL</a> the
user agent must use the following steps. Resolving a URL can result
@@ -5575,8 +5575,13 @@
<p>Every XML and HTML document in an HTML UA is represented by a
<code>Document</code> object. <a href=#refsDOM3CORE>[DOM3CORE]</a></p>
+ <p><dfn id="the-document's-address">The document's address</dfn> is an <a href=#absolute-url>absolute URL</a>
+ that is set when the <code>Document</code> is created.</p>
- <h4 id=documents-in-the-dom><span class=secno>3.2.1 </span>Documents in the DOM</h4>
+ <p>When a <code>Document</code> is created by a script using the
+ <code title="">createDocument()</code> API, <a href="#the-document's-address">the document's
+ address</a> is the same as <a href="#the-document's-address">the document's address</a> of
+ the <a href=#script-document-context>script document context</a> of that script.</p>
<p><code>Document</code> objects are assumed to be <dfn id=xml-documents>XML
documents</dfn> unless they are flagged as being <dfn id=html-documents>HTML
@@ -5588,6 +5593,10 @@
<code>DOMImplementation</code> object is initially an <a href=#xml-documents title="XML documents">XML document</a>, but can be made into an
<a href=#html-documents title="HTML documents">HTML document</a> by calling <code title=dom-document-open><a href=#dom-document-open>document.open()</a></code> on it.</p>
+
+
+ <h4 id=documents-in-the-dom><span class=secno>3.2.1 </span>Documents in the DOM</h4>
+
<p>All <code>Document</code> objects (in user agents implementing
this specification) must also implement the
<code><a href=#htmldocument>HTMLDocument</a></code> interface, available using
@@ -5679,15 +5688,13 @@
<h4 id=resource-metadata-management><span class=secno>3.2.3 </span><dfn>Resource metadata management</dfn></h4>
<p>The <dfn id=dom-document-url title=dom-document-URL><code>URL</code></dfn>
- attribute must return <span>the document's address</span><!--
- XXXDOCURL xref -->.</p>
+ attribute must return <a href="#the-document's-address">the document's address</a>.</p>
-
<p>The <dfn id=dom-document-referrer title=dom-document-referrer><code>referrer</code></dfn> attribute
- must return either the <span title="the document's
- address">address</span><!-- XXXDOXURL xref --> of the <a href=#active-document>active
- document</a> of the <a href=#source-browsing-context>source browsing context</a> at the
- time the navigation was started (that is, the page which <a href=#navigate title=navigate>navigated</a> the <a href=#browsing-context>browsing context</a>
+ must return either the <a href="#the-document's-address" title="the document's
+ address">address</a> of the <a href=#active-document>active document</a> of the
+ <a href=#source-browsing-context>source browsing context</a> at the time the navigation was
+ started (that is, the page which <a href=#navigate title=navigate>navigated</a> the <a href=#browsing-context>browsing context</a>
to the current document), or the empty string if there is no such
originating page, or if the UA has been configured not to report
referrers in this case, or if the navigation was initiated for a
@@ -5702,7 +5709,6 @@
and the current page does not (e.g. when navigating from an <code title="">https:</code> page to an <code title="">http:</code>
page).</p>
-
<hr><p>The <dfn id=dom-document-cookie title=dom-document-cookie><code>cookie</code></dfn>
attribute represents the cookies of the resource.</p>
@@ -5714,29 +5720,27 @@
<p id=sandboxCookies>On getting, if the <a href=#sandboxed-origin-browsing-context-flag>sandboxed origin
browsing context flag</a> is set on the <a href=#browsing-context>browsing
context</a> of the document, the user agent must raise a
- <code><a href=#security_err>SECURITY_ERR</a></code> exception. Otherwise, it must return the same
- string as the value of the <code title="">Cookie</code> HTTP header
- it would include if <a href=#fetch title=fetch>fetching</a> the resource
- indicated by <span>the document's address</span><!-- XXXDOCURL -->
- over HTTP, as per RFC 2109 section 4.3.4 or later specifications. <a href=#refsRFC2109>[RFC2109]</a> <a href=#refsRFC2965>[RFC2965]</a></p>
+ <code><a href=#security_err>SECURITY_ERR</a></code> exception. Otherwise, it must return the
+ same string as the value of the <code title="">Cookie</code> HTTP
+ header it would include if <a href=#fetch title=fetch>fetching</a> the
+ resource indicated by <a href="#the-document's-address">the document's address</a> over HTTP,
+ as per RFC 2109 section 4.3.4 or later specifications. <a href=#refsRFC2109>[RFC2109]</a> <a href=#refsRFC2965>[RFC2965]</a></p>
<p>On setting, if the <a href=#sandboxed-origin-browsing-context-flag>sandboxed origin browsing context
flag</a> is set on the <a href=#browsing-context>browsing context</a> of the
document, the user agent must raise a <code><a href=#security_err>SECURITY_ERR</a></code>
- exception. Otherwise, the user agent must act as it would
- when processing cookies if it had just attempted to
- <a href=#fetch>fetch</a> <span>the document's address</span><!-- XXXDOCURL
- --> over HTTP, and had received a response with a
- <code>Set-Cookie</code> header whose value was the specified value,
- as per RFC 2109 sections 4.3.1, 4.3.2, and 4.3.3 or later
- specifications. <a href=#refsRFC2109>[RFC2109]</a> <a href=#refsRFC2965>[RFC2965]</a></p>
+ exception. Otherwise, the user agent must act as it would when
+ processing cookies if it had just attempted to <a href=#fetch>fetch</a>
+ <a href="#the-document's-address">the document's address</a> over HTTP, and had received a
+ response with a <code>Set-Cookie</code> header whose value was the
+ specified value, as per RFC 2109 sections 4.3.1, 4.3.2, and 4.3.3 or
+ later specifications. <a href=#refsRFC2109>[RFC2109]</a> <a href=#refsRFC2965>[RFC2965]</a></p>
<p class=note>Since the <code title=dom-document-cookie><a href=#dom-document-cookie>cookie</a></code> attribute is accessible
across frames, the path restrictions on cookies are only a tool to
help manage which cookies are sent to which parts of the site, and
are not in any way a security feature.</p>
-
<hr><p>The <dfn id=dom-document-lastmodified title=dom-document-lastModified><code>lastModified</code></dfn>
attribute, on getting, must return the date and time of the
<code>Document</code>'s source file's last modification, in the
@@ -15369,7 +15373,7 @@
<p>If the <code title=attr-iframe-src><a href=#attr-iframe-src>src</a></code> attribute is not
set when the element is created, the browsing context will remain at
- the initial <code><a href=#about:blank>about:blank</a></code><!-- XXX xref --> page.</p>
+ the initial <code><a href=#about:blank>about:blank</a></code> page.</p>
<p>The <dfn id=attr-iframe-name title=attr-iframe-name><code>name</code></dfn>
attribute, if present, must be a <a href=#valid-browsing-context-name>valid browsing context
@@ -15566,8 +15570,8 @@
while the <a href=#browsing-context>browsing context</a>'s <a href=#active-document>active
document</a> has the <a href=#same-origin>same origin</a> as the
<code><a href=#the-iframe-element>iframe</a></code> element's document, or the <a href=#browsing-context>browsing
- context</a>'s <a href=#active-document>active document</a>'s <em><span title="the
- document's address">address</span><!-- XXX xref --></em> has the
+ context</a>'s <a href=#active-document>active document</a>'s <em><a href="#the-document's-address" title="the
+ document's address">address</a><!-- XXX xref --></em> has the
<a href=#same-origin>same origin</a> as the <code><a href=#the-iframe-element>iframe</a></code> element's
document, the following requirements apply:</p>
@@ -28691,8 +28695,7 @@
<li>
- <p>If <var title="">action</var> is the empty string, let <var title="">action</var> be <span>the document's address</span><!--
- XXXDOCURL -->.</p>
+ <p>If <var title="">action</var> is the empty string, let <var title="">action</var> be <a href="#the-document's-address">the document's address</a>.</p>
<p class=note>This step is a willful violation of RFC 3986. <a href=#refsRFC3986>[RFC3986]</a></p>
@@ -31199,9 +31202,8 @@
<p>The <i>action</i> of the <i title=attr-bb-type-makeapp-state><a href=#the-make-application-state>make application</a></i> state is to
confirm the user's intent to use the current site in a standalone
fashion, and, provided the user's intent is confirmed, offer the
- user a way to make the resource identified by <span>the document's
- address</span><!-- XXXDOCURL xref --> available in such a
- fashion.</p>
+ user a way to make the resource identified by <a href="#the-document's-address">the document's
+ address</a> available in such a fashion.</p>
<p class=warning>The confirmation is needed because it is
relatively easy to trick users into activating buttons. The
@@ -32139,16 +32141,13 @@
<p>When a <a href=#browsing-context>browsing context</a> is first created, it must be
created with a single <code>Document</code> in its session history,
- whose <span title="the document's address">address</span><!--
- XXXDOCURL --> is <code><a href=#about:blank>about:blank</a></code><!-- XXX xref -->, which is
- marked as being an <a href=#html-documents title="HTML documents">HTML
- document</a>, and whose <a href="#document's-character-encoding" title="document's character
- encoding">character encoding</a> is UTF-8. The
- <code>Document</code> must have a single child <code><a href=#the-html-element>html</a></code>
- node, which itself has a single child <code><a href=#the-body-element>body</a></code> node. If the
- <a href=#browsing-context>browsing context</a> is created specifically to be
- immediately navigated, then that initial navigation will have
- <a href=#replacement-enabled>replacement enabled</a>.</p>
+ whose <a href="#the-document's-address" title="the document's address">address</a> is
+ <code><a href=#about:blank>about:blank</a></code>, which is marked as being an <a href=#html-documents title="HTML documents">HTML document</a>, and whose <a href="#document's-character-encoding" title="document's character encoding">character encoding</a> is
+ UTF-8. The <code>Document</code> must have a single child
+ <code><a href=#the-html-element>html</a></code> node, which itself has a single child
+ <code><a href=#the-body-element>body</a></code> node. If the <a href=#browsing-context>browsing context</a> is
+ created specifically to be immediately navigated, then that initial
+ navigation will have <a href=#replacement-enabled>replacement enabled</a>.</p>
<p id=about-blank-origin>The <a href=#origin-0>origin</a> of the
<code><a href=#about:blank>about:blank</a></code> <code>Document</code> is set when the
@@ -32624,8 +32623,7 @@
<a href=#valid-url>valid URL</a> for a page to load in the browsing
context. If no arguments are provided, or if the first argument is
the empty string, then the <var title="">url</var> argument defaults
- to "<code><a href=#about:blank>about:blank</a></code><!-- XXX xref -->". The argument must be
- <a href=#resolve-a-url title="resolve a url">resolved</a> to an <a href=#absolute-url>absolute
+ to "<code><a href=#about:blank>about:blank</a></code>". The argument must be <a href=#resolve-a-url title="resolve a url">resolved</a> to an <a href=#absolute-url>absolute
URL</a> (or an error) when the method is invoked.</p>
<p>The second argument, <var title="">target</var>, specifies the
@@ -32897,8 +32895,9 @@
server-based naming authority</dt>
<dd>The <a href=#origin-0>origin</a> is the <a href=#origin-0>origin</a> of the
- <span title="the document's address">address</span><!-- XXXDOCURL
- --> of the <code>Document</code> or image.</dd>
+ <a href="#the-document's-address" title="the document's address">address</a> of the
+ <code>Document</code> or the <a href=#url>URL</a> of the image, as
+ appropriate.</dd>
<dt>If a <code>Document</code> or image was generated from a
@@ -32917,8 +32916,8 @@
<code>Document</code> or script in which the <code title="">data:</code> URL was found.</dd>
- <dt>If a <code>Document</code> has the <span title="the
- document's address">address</span><!-- XXXDOCURL -->
+ <dt>If a <code>Document</code> has the <a href="#the-document's-address" title="the
+ document's address">address</a>
"<code><a href=#about:blank>about:blank</a></code>"</dt>
<dd>The <a href=#origin-0>origin</a> of the <code>Document</code> is <a href=#about-blank-origin>the <span>origin</span> it was
@@ -36393,9 +36392,8 @@
abort the <code title=dom-history-pushState><a href=#dom-history-pushstate>pushState()</a></code>
steps.</li>
- <li>Compare the resulting <a href=#absolute-url>absolute URL</a> to <span>the
- document's address</span><!-- XXXDOCURL -->. If any part of these
- two <a href=#url title=URL>URLs</a> differ other than the <a href=#url-path title=url-path><path></a>, <a href=#url-query title=url-query><query></a>, and <a href=#url-fragment title=url-fragment><fragment></a> components, then
+ <li>Compare the resulting <a href=#absolute-url>absolute URL</a> to <a href="#the-document's-address">the
+ document's address</a>. If any part of these two <a href=#url title=URL>URLs</a> differ other than the <a href=#url-path title=url-path><path></a>, <a href=#url-query title=url-query><query></a>, and <a href=#url-fragment title=url-fragment><fragment></a> components, then
raise a <code><a href=#security_err>SECURITY_ERR</a></code> exception and abort the <code title=dom-history-pushState><a href=#dom-history-pushstate>pushState()</a></code> steps.</li>
</ol><p>For the purposes of the comparison in the above substeps, the
@@ -36503,7 +36501,7 @@
<code><a href=#location>Location</a></code> object for that <code><a href=#window>Window</a></code> object's
<a href=#active-document>active document</a>.</p>
- <p><code><a href=#location>Location</a></code> objects provide a representation of <span title="the document's address">their document's address</span>, and
+ <p><code><a href=#location>Location</a></code> objects provide a representation of <a href="#the-document's-address" title="the document's address">their document's address</a>, and
allow the <a href=#current-entry>current entry</a> of the <a href=#browsing-context>browsing
context</a>'s session history to be changed, by adding or
replacing entries in the <code title=dom-history><a href=#dom-history>history</a></code>
@@ -36529,10 +36527,9 @@
};</pre>
<p>The <dfn id=dom-location-href title=dom-location-href><code>href</code></dfn>
- attribute must return <span title="the document's address">the
- address</span><!-- XXXDOCURL --> of the page represented by the
- associated <code>Document</code> object, as an <a href=#absolute-url>absolute
- URL</a>.</p>
+ attribute must return <a href="#the-document's-address" title="the document's address">the
+ address</a> of the associated <code>Document</code> object, as an
+ <a href=#absolute-url>absolute URL</a>.</p>
<p>On setting, <!--XXX Mozilla does this, but IE doesn't. What
should we do?: the behavior depends on the context in which the
@@ -36580,12 +36577,13 @@
<p>The <code><a href=#location>Location</a></code> interface also has the complement of
<a href=#url-decomposition-attributes>URL decomposition attributes</a>, <dfn id=dom-location-protocol title=dom-location-protocol><code>protocol</code></dfn>, <dfn id=dom-location-host title=dom-location-host><code>host</code></dfn>, <dfn id=dom-location-port title=dom-location-port><code>port</code></dfn>, <dfn id=dom-location-hostname title=dom-location-hostname><code>hostname</code></dfn>, <dfn id=dom-location-pathname title=dom-location-pathname><code>pathname</code></dfn>, <dfn id=dom-location-search title=dom-location-search><code>search</code></dfn>, and <dfn id=dom-location-hash title=dom-location-hash><code>hash</code></dfn>. These must follow
- the rules given for URL decomposition attributes, with the <a href=#concept-uda-input title=concept-uda-input>input</a> being <span title="the
- document's address">the address</span><!-- XXXDOCURL --> of the page
- represented by the associated <code>Document</code> object, as an
- <a href=#absolute-url>absolute URL</a> (same as the <code title=dom-location-href><a href=#dom-location-href>href</a></code> attribute), and the <a href=#concept-uda-setter title=concept-uda-setter>common setter action</a> being the
- same as setting the <code title=dom-location-href><a href=#dom-location-href>href</a></code>
- attribute to the new output value.</p>
+ the rules given for URL decomposition attributes, with the <a href=#concept-uda-input title=concept-uda-input>input</a> being <a href="#the-document's-address" title="the
+ document's address">the address</a> of the associated
+ <code>Document</code> object, as an <a href=#absolute-url>absolute URL</a> (same
+ as the <code title=dom-location-href><a href=#dom-location-href>href</a></code> attribute), and
+ the <a href=#concept-uda-setter title=concept-uda-setter>common setter action</a>
+ being the same as setting the <code title=dom-location-href><a href=#dom-location-href>href</a></code> attribute to the new output
+ value.</p>
<hr><p>The <dfn id=dom-location-resolveurl title=dom-location-resolveURL><code>resolveURL(<var title="">url</var>)</code></dfn> method must <a href=#resolve-a-url title="resolve a
url">resolve</a> its <var title="">url</var> argument, and if
@@ -36705,10 +36703,9 @@
<li id=navigate-fragid-step><p><i>Fragment identifiers</i>: If
the <a href=#absolute-url>absolute URL</a> of the new resource is the same as
- the <span title="the document's
- address">address</span><!--XXXDOCURL--> of the <a href=#active-document>active
- document</a> of the <a href=#browsing-context>browsing context</a> being
- navigated, ignoring any <a href=#url-fragment title=url-fragment><fragment></a> components of those
+ the <a href="#the-document's-address" title="the document's address">address</a> of the
+ <a href=#active-document>active document</a> of the <a href=#browsing-context>browsing context</a>
+ being navigated, ignoring any <a href=#url-fragment title=url-fragment><fragment></a> components of those
<a href=#url title=URL>URLs</a>, and the new resource is to be
fetched using HTTP GET or equivalent, then <a href=#scroll-to-fragid title=navigate-fragid>navigate to that fragment identifier</a>
and abort these steps.</li>
@@ -36803,11 +36800,10 @@
URL of the resource that was requested (the one that matched the
<a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback
namespace</a>), not the fallback resource, as the resource's
- <span title="the document's address">address</span><!-- XXXDOCURL
- -->. However, the user agent may indicate to the user that the
- original page load failed, that the page used was a fallback
- resource, and what the URL of the fallback resource actually
- is.</p>
+ <a href="#the-document's-address" title="the document's address">address</a>. However, the
+ user agent may indicate to the user that the original page load
+ failed, that the page used was a fallback resource, and what the
+ URL of the fallback resource actually is.</p>
</li>
@@ -36865,8 +36861,18 @@
<dd>Follow the steps given in the <a href=#read-plugin title=navigate-plugin>plugin</a> section, and abort these
steps.</dd>
- </dl></li>
+ </dl><p>Any <code>Document</code> created by these steps must have its
+ <a href="#the-document's-address" title="the document's address">address</a> set to the
+ <a href=#url>URL</a> that was originally to be <a href=#fetch title=fetch>fetched</a>, ignoring any other data that was
+ used to obtain the resource (e.g. the entity body in the case of a
+ POST submission is not part of <a href="#the-document's-address">the document's
+ address</a>, nor is the URL of the fallback resource in the
+ case of the original load having failed and that URL having been
+ found to match a <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback
+ namespace</a>).</p>
+ </li>
+
<li id=navigate-non-Document><p><i>Non-document content</i>: If,
given <var title="">type</var>, the new resource is to be handled
by displaying some sort of inline content, e.g. a native rendering
@@ -37178,7 +37184,7 @@
identifier, then the user agent must <a href=#update-the-session-history-with-the-new-page>update the session
history with the new page</a>, where "the new page" has the same
<code>Document</code> as before but with the URL having the newly
- specified fragment identifier.</p><!-- XXXDOCURL ? -->
+ specified fragment identifier.</p>
<p>Part of that algorithm involves the user agent having to
<a href=#scroll-to-the-fragment-identifier>scroll to the fragment identifier</a>, which is the
@@ -38632,29 +38638,27 @@
authentication headers must be included in the request. Which other
headers are required depends on the URLs involved.</p>
- <dl class=switch><dt>If both the <span title="the document's
- address">address</span><!-- XXXDOCURL --> of the
- <code>Document</code> object containing the hyperlink being audited
- and the ping URL have the <a href=#same-origin>same origin</a></dt>
+ <dl class=switch><dt>If both the <a href="#the-document's-address" title="the document's address">address</a>
+ of the <code>Document</code> object containing the hyperlink being
+ audited and the ping URL have the <a href=#same-origin>same origin</a></dt>
<dd>The request must include a <code title="">Ping-From</code> HTTP
- header with, as its value, the <span title="the document's
- address">address</span><!-- XXXDOCURL --> of the document
- containing the hyperlink, and a <code title="">Ping-To</code> HTTP
- header with, as its value, the address of the <a href=#absolute-url>absolute
- URL</a> of the target of the hyperlink. The request must not
- include a <code title="">Referer</code> HTTP header.</dd>
+ header with, as its value, the <a href="#the-document's-address" title="the document's
+ address">address</a> of the document containing the hyperlink,
+ and a <code title="">Ping-To</code> HTTP header with, as its value,
+ the address of the <a href=#absolute-url>absolute URL</a> of the target of the
+ hyperlink. The request must not include a <code title="">Referer</code> HTTP header. <!-- why not? --></dd>
<dt>Otherwise, if the origins are different, but the document
containing the hyperlink being audited was not retrieved over an
- encrypted connection</dt>
+ encrypted connection</dt> <!-- why different? -->
<dd>The request must include a <code title="">Referer</code> HTTP
- header [sic] with, as its value, the location of the document
- containing the hyperlink, a <code title="">Ping-From</code> HTTP
- header with the same value, and a <code title="">Ping-To</code>
- HTTP header with, as its value, the address of the target of the
- hyperlink.</dd>
+ header [sic] with, as its value, the <a href="#the-document's-address" title="the document's
+ address">address</a> of the document containing the hyperlink, a
+ <code title="">Ping-From</code> HTTP header with the same value,
+ and a <code title="">Ping-To</code> HTTP header with, as its value,
+ the address of the target of the hyperlink.</dd>
<dt>Otherwise, the origins are different and the document
containing the hyperlink being audited was retrieved over an
Modified: source
===================================================================
--- source 2008-11-26 23:14:05 UTC (rev 2467)
+++ source 2008-11-27 02:00:31 UTC (rev 2468)
@@ -3567,22 +3567,21 @@
child of <span>the <code>head</code> element</span> and has an
<code title="attr-base-href">href</code> attribute, then the
<span>document base URL</span> is <span>the document's
- address</span><!-- XXXDOCURL -->.</p></li>
+ address</span>.</p></li>
<li><p>Otherwise, let <var title="">url</var> be the value of the
<code title="attr-base-href">href</code> attribute of the first such
element.</p></li>
<li><p><span title="resolve a URL">Resolve</span> the <var
- title="">url</var> URL, using <span>the document's
- address</span><!-- XXXDOCURL --> as the <span>base URL</span>
- (thus, the <code>base</code> <code
- title="attr-base-href">href</code> attribute isn't affect by <code
- title="attr-xml-base">xml:base</code> attributes).</p></li>
+ title="">url</var> URL, using <span>the document's address</span>
+ as the <span>base URL</span> (thus, the <code>base</code> <code
+ title="attr-base-href">href</code> attribute isn't affected by
+ <code title="attr-xml-base">xml:base</code> attributes).</p></li>
<li><p>The <span>document base URL</span> is the result of the
previous step if it was successful; otherwise it is <span>the
- document's address</span><!-- XXXDOCURL -->.</p></li>
+ document's address</span>.</p></li>
</ol>
@@ -5568,8 +5567,13 @@
<code>Document</code> object. <a
href="#refsDOM3CORE">[DOM3CORE]</a></p>
+ <p><dfn>The document's address</dfn> is an <span>absolute URL</span>
+ that is set when the <code>Document</code> is created.</p>
- <h4>Documents in the DOM</h4>
+ <p>When a <code>Document</code> is created by a script using the
+ <code title="">createDocument()</code> API, <span>the document's
+ address</span> is the same as <span>the document's address</span> of
+ the <span>script document context</span> of that script.</p>
<p><code>Document</code> objects are assumed to be <dfn>XML
documents</dfn> unless they are flagged as being <dfn>HTML
@@ -5586,6 +5590,10 @@
<span title="HTML documents">HTML document</span> by calling <code
title="dom-document-open">document.open()</code> on it.</p>
+
+
+ <h4>Documents in the DOM</h4>
+
<p>All <code>Document</code> objects (in user agents implementing
this specification) must also implement the
<code>HTMLDocument</code> interface, available using
@@ -5677,16 +5685,14 @@
<h4><dfn>Resource metadata management</dfn></h4>
<p>The <dfn title="dom-document-URL"><code>URL</code></dfn>
- attribute must return <span>the document's address</span><!--
- XXXDOCURL xref -->.</p>
+ attribute must return <span>the document's address</span>.</p>
-
<p>The <dfn
title="dom-document-referrer"><code>referrer</code></dfn> attribute
must return either the <span title="the document's
- address">address</span><!-- XXXDOXURL xref --> of the <span>active
- document</span> of the <span>source browsing context</span> at the
- time the navigation was started (that is, the page which <span
+ address">address</span> of the <span>active document</span> of the
+ <span>source browsing context</span> at the time the navigation was
+ started (that is, the page which <span
title="navigate">navigated</span> the <span>browsing context</span>
to the current document), or the empty string if there is no such
originating page, or if the UA has been configured not to report
@@ -5705,7 +5711,6 @@
title="">https:</code> page to an <code title="">http:</code>
page).</p>
-
<hr>
<p>The <dfn title="dom-document-cookie"><code>cookie</code></dfn>
@@ -5719,24 +5724,23 @@
<p id="sandboxCookies">On getting, if the <span>sandboxed origin
browsing context flag</span> is set on the <span>browsing
context</span> of the document, the user agent must raise a
- <code>SECURITY_ERR</code> exception. Otherwise, it must return the same
- string as the value of the <code title="">Cookie</code> HTTP header
- it would include if <span title="fetch">fetching</span> the resource
- indicated by <span>the document's address</span><!-- XXXDOCURL -->
- over HTTP, as per RFC 2109 section 4.3.4 or later specifications. <a
+ <code>SECURITY_ERR</code> exception. Otherwise, it must return the
+ same string as the value of the <code title="">Cookie</code> HTTP
+ header it would include if <span title="fetch">fetching</span> the
+ resource indicated by <span>the document's address</span> over HTTP,
+ as per RFC 2109 section 4.3.4 or later specifications. <a
href="#refsRFC2109">[RFC2109]</a> <a
href="#refsRFC2965">[RFC2965]</a></p>
<p>On setting, if the <span>sandboxed origin browsing context
flag</span> is set on the <span>browsing context</span> of the
document, the user agent must raise a <code>SECURITY_ERR</code>
- exception. Otherwise, the user agent must act as it would
- when processing cookies if it had just attempted to
- <span>fetch</span> <span>the document's address</span><!-- XXXDOCURL
- --> over HTTP, and had received a response with a
- <code>Set-Cookie</code> header whose value was the specified value,
- as per RFC 2109 sections 4.3.1, 4.3.2, and 4.3.3 or later
- specifications. <a href="#refsRFC2109">[RFC2109]</a> <a
+ exception. Otherwise, the user agent must act as it would when
+ processing cookies if it had just attempted to <span>fetch</span>
+ <span>the document's address</span> over HTTP, and had received a
+ response with a <code>Set-Cookie</code> header whose value was the
+ specified value, as per RFC 2109 sections 4.3.1, 4.3.2, and 4.3.3 or
+ later specifications. <a href="#refsRFC2109">[RFC2109]</a> <a
href="#refsRFC2965">[RFC2965]</a></p>
<p class="note">Since the <code
@@ -5745,7 +5749,6 @@
help manage which cookies are sent to which parts of the site, and
are not in any way a security feature.</p>
-
<hr>
<p>The <dfn
@@ -16411,7 +16414,7 @@
<p>If the <code title="attr-iframe-src">src</code> attribute is not
set when the element is created, the browsing context will remain at
- the initial <code>about:blank</code><!-- XXX xref --> page.</p>
+ the initial <code>about:blank</code> page.</p>
<p>The <dfn title="attr-iframe-name"><code>name</code></dfn>
attribute, if present, must be a <span>valid browsing context
@@ -32379,8 +32382,7 @@
<li>
<p>If <var title="">action</var> is the empty string, let <var
- title="">action</var> be <span>the document's address</span><!--
- XXXDOCURL -->.</p>
+ title="">action</var> be <span>the document's address</span>.</p>
<p class="note">This step is a willful violation of RFC 3986. <a
href="#refsRFC3986">[RFC3986]</a></p>
@@ -35453,8 +35455,7 @@
confirm the user's intent to use the current site in a standalone
fashion, and, provided the user's intent is confirmed, offer the
user a way to make the resource identified by <span>the document's
- address</span><!-- XXXDOCURL xref --> available in such a
- fashion.</p>
+ address</span> available in such a fashion.</p>
<p class="warning">The confirmation is needed because it is
relatively easy to trick users into activating buttons. The
@@ -36543,16 +36544,15 @@
<p>When a <span>browsing context</span> is first created, it must be
created with a single <code>Document</code> in its session history,
- whose <span title="the document's address">address</span><!--
- XXXDOCURL --> is <code>about:blank</code><!-- XXX xref -->, which is
- marked as being an <span title="HTML documents">HTML
- document</span>, and whose <span title="document's character
- encoding">character encoding</span> is UTF-8. The
- <code>Document</code> must have a single child <code>html</code>
- node, which itself has a single child <code>body</code> node. If the
- <span>browsing context</span> is created specifically to be
- immediately navigated, then that initial navigation will have
- <span>replacement enabled</span>.</p>
+ whose <span title="the document's address">address</span> is
+ <code>about:blank</code>, which is marked as being an <span
+ title="HTML documents">HTML document</span>, and whose <span
+ title="document's character encoding">character encoding</span> is
+ UTF-8. The <code>Document</code> must have a single child
+ <code>html</code> node, which itself has a single child
+ <code>body</code> node. If the <span>browsing context</span> is
+ created specifically to be immediately navigated, then that initial
+ navigation will have <span>replacement enabled</span>.</p>
<p id="about-blank-origin">The <span>origin</span> of the
<code>about:blank</code> <code>Document</code> is set when the
@@ -37091,8 +37091,8 @@
<span>valid URL</span> for a page to load in the browsing
context. If no arguments are provided, or if the first argument is
the empty string, then the <var title="">url</var> argument defaults
- to "<code>about:blank</code><!-- XXX xref -->". The argument must be
- <span title="resolve a url">resolved</span> to an <span>absolute
+ to "<code>about:blank</code>". The argument must be <span
+ title="resolve a url">resolved</span> to an <span>absolute
URL</span> (or an error) when the method is invoked.</p>
<p>The second argument, <var title="">target</var>, specifies the
@@ -37399,8 +37399,9 @@
server-based naming authority</dt>
<dd>The <span>origin</span> is the <span>origin</span> of the
- <span title="the document's address">address</span><!-- XXXDOCURL
- --> of the <code>Document</code> or image.</dd>
+ <span title="the document's address">address</span> of the
+ <code>Document</code> or the <span>URL</span> of the image, as
+ appropriate.</dd>
<dt>If a <code>Document</code> or image was generated from a
@@ -37422,7 +37423,7 @@
<dt>If a <code>Document</code> has the <span title="the
- document's address">address</span><!-- XXXDOCURL -->
+ document's address">address</span>
"<code>about:blank</code>"</dt>
<dd>The <span>origin</span> of the <code>Document</code> is <a
@@ -41418,8 +41419,8 @@
steps.</li>
<li>Compare the resulting <span>absolute URL</span> to <span>the
- document's address</span><!-- XXXDOCURL -->. If any part of these
- two <span title="URL">URLs</span> differ other than the <span
+ document's address</span>. If any part of these two <span
+ title="URL">URLs</span> differ other than the <span
title="url-path"><path></span>, <span
title="url-query"><query></span>, and <span
title="url-fragment"><fragment></span> components, then
@@ -41583,9 +41584,8 @@
<p>The <dfn title="dom-location-href"><code>href</code></dfn>
attribute must return <span title="the document's address">the
- address</span><!-- XXXDOCURL --> of the page represented by the
- associated <code>Document</code> object, as an <span>absolute
- URL</span>.</p>
+ address</span> of the associated <code>Document</code> object, as an
+ <span>absolute URL</span>.</p>
<p>On setting, <!--XXX Mozilla does this, but IE doesn't. What
should we do?: the behavior depends on the context in which the
@@ -41647,13 +41647,13 @@
title="dom-location-hash"><code>hash</code></dfn>. These must follow
the rules given for URL decomposition attributes, with the <span
title="concept-uda-input">input</span> being <span title="the
- document's address">the address</span><!-- XXXDOCURL --> of the page
- represented by the associated <code>Document</code> object, as an
- <span>absolute URL</span> (same as the <code
- title="dom-location-href">href</code> attribute), and the <span
- title="concept-uda-setter">common setter action</span> being the
- same as setting the <code title="dom-location-href">href</code>
- attribute to the new output value.</p>
+ document's address">the address</span> of the associated
+ <code>Document</code> object, as an <span>absolute URL</span> (same
+ as the <code title="dom-location-href">href</code> attribute), and
+ the <span title="concept-uda-setter">common setter action</span>
+ being the same as setting the <code
+ title="dom-location-href">href</code> attribute to the new output
+ value.</p>
<hr>
@@ -41789,10 +41789,9 @@
<li id="navigate-fragid-step"><p><i>Fragment identifiers</i>: If
the <span>absolute URL</span> of the new resource is the same as
- the <span title="the document's
- address">address</span><!--XXXDOCURL--> of the <span>active
- document</span> of the <span>browsing context</span> being
- navigated, ignoring any <span
+ the <span title="the document's address">address</span> of the
+ <span>active document</span> of the <span>browsing context</span>
+ being navigated, ignoring any <span
title="url-fragment"><fragment></span> components of those
<span title="URL">URLs</span>, and the new resource is to be
fetched using HTTP GET or equivalent, then <span
@@ -41899,11 +41898,10 @@
URL of the resource that was requested (the one that matched the
<span title="concept-appcache-fallback-ns">fallback
namespace</span>), not the fallback resource, as the resource's
- <span title="the document's address">address</span><!-- XXXDOCURL
- -->. However, the user agent may indicate to the user that the
- original page load failed, that the page used was a fallback
- resource, and what the URL of the fallback resource actually
- is.</p>
+ <span title="the document's address">address</span>. However, the
+ user agent may indicate to the user that the original page load
+ failed, that the page used was a fallback resource, and what the
+ URL of the fallback resource actually is.</p>
</li>
@@ -41971,6 +41969,18 @@
</dl>
+ <p>Any <code>Document</code> created by these steps must have its
+ <span title="the document's address">address</span> set to the
+ <span>URL</span> that was originally to be <span
+ title="fetch">fetched</span>, ignoring any other data that was
+ used to obtain the resource (e.g. the entity body in the case of a
+ POST submission is not part of <span>the document's
+ address</span>, nor is the URL of the fallback resource in the
+ case of the original load having failed and that URL having been
+ found to match a <span
+ title="concept-appcache-fallback-ns">fallback
+ namespace</span>).</p>
+
</li>
<li id="navigate-non-Document"><p><i>Non-document content</i>: If,
@@ -42324,7 +42334,7 @@
identifier, then the user agent must <span>update the session
history with the new page</span>, where "the new page" has the same
<code>Document</code> as before but with the URL having the newly
- specified fragment identifier.</p><!-- XXXDOCURL ? -->
+ specified fragment identifier.</p>
<p>Part of that algorithm involves the user agent having to
<span>scroll to the fragment identifier</span>, which is the
@@ -43945,29 +43955,28 @@
<dl class="switch">
- <dt>If both the <span title="the document's
- address">address</span><!-- XXXDOCURL --> of the
- <code>Document</code> object containing the hyperlink being audited
- and the ping URL have the <span>same origin</span></dt>
+ <dt>If both the <span title="the document's address">address</span>
+ of the <code>Document</code> object containing the hyperlink being
+ audited and the ping URL have the <span>same origin</span></dt>
<dd>The request must include a <code title="">Ping-From</code> HTTP
header with, as its value, the <span title="the document's
- address">address</span><!-- XXXDOCURL --> of the document
- containing the hyperlink, and a <code title="">Ping-To</code> HTTP
- header with, as its value, the address of the <span>absolute
- URL</span> of the target of the hyperlink. The request must not
- include a <code title="">Referer</code> HTTP header.</dd>
+ address">address</span> of the document containing the hyperlink,
+ and a <code title="">Ping-To</code> HTTP header with, as its value,
+ the address of the <span>absolute URL</span> of the target of the
+ hyperlink. The request must not include a <code
+ title="">Referer</code> HTTP header. <!-- why not? --></dd>
<dt>Otherwise, if the origins are different, but the document
containing the hyperlink being audited was not retrieved over an
- encrypted connection</dt>
+ encrypted connection</dt> <!-- why different? -->
<dd>The request must include a <code title="">Referer</code> HTTP
- header [sic] with, as its value, the location of the document
- containing the hyperlink, a <code title="">Ping-From</code> HTTP
- header with the same value, and a <code title="">Ping-To</code>
- HTTP header with, as its value, the address of the target of the
- hyperlink.</dd>
+ header [sic] with, as its value, the <span title="the document's
+ address">address</span> of the document containing the hyperlink, a
+ <code title="">Ping-From</code> HTTP header with the same value,
+ and a <code title="">Ping-To</code> HTTP header with, as its value,
+ the address of the target of the hyperlink.</dd>
<dt>Otherwise, the origins are different and the document
containing the hyperlink being audited was retrieved over an
More information about the Commit-Watchers
mailing list