- From: poot <cvsmail@w3.org>
- Date: Thu, 27 Nov 2008 11:04:01 +0900 (JST)
- To: public-html-diffs@w3.org
Define 'the document's address'. (whatwg r2468)
5.9.8 Navigating to a fragment identifier
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#scroll-to-fragid
A vocabulary and associated APIs for HTML and XHTML
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#a-vocabulary-and-associated-apis-for-html-and-xhtml
PARSE_ERR
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#parse_err
protocol
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#dom-location-protocol
seamless browsing context flag
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#seamless-browsing-context-flag
document base URL
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#document-base-url
default view
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#default-view
The origin of the about:blank Document is set when the Document is created, in a manner dependent on whether the browsing context created is a nested browsing context, as follows:
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#about-blank-origin
HTML documents
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#html-documents
resolveURL(url)
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#dom-location-resolveurl
location
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#dom-location
name
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#attr-iframe-name
5.2.2 APIs for creating and navigating browsing contexts by name
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#apis-for-creating-and-navigating-browsing-contexts-by-name
If a Document is in a browsing context whose sandboxed origin browsing context flag is set
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#sandboxOrigin
On getting, if the sandboxed origin browsing context flag is set on the browsing context of the document, the user agent must raise a SECURITY_ERR exception. Otherwise, it must return the same string as the value of the Cookie HTTP header it would include if fetching the resource indicated by the document's address over HTTP, as per RFC 2109 section 4.3.4 or later specifications. [RFC2109] [RFC2965]
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#sandboxCookies
The document's address
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#the-document-s-address
If the source browsing context is the same as the browsing context being navigated, and this browsing context has its seamless browsing context flag set, then find the nearest ancestor browsing context that does not have its seamless browsing context flag set, and continue these steps as if that browsing context was the one that was going to be navigated instead.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#seamlessLinks
referrer
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#dom-document-referrer
Location
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#location
href
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#dom-location-href
5.11.2.1 Hyperlink auditing
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#hyperlink-auditing
SERIALISE_ERR
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#serialise_err
seamless
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#attr-iframe-seamless
resolve a URL
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#resolve-a-url
Fragment identifiers: If the absolute URL of the new resource is the same as the address of the active document of the browsing context being navigated, ignoring any <fragment> components of those URLs, and the new resource is to be fetched using HTTP GET or equivalent, then navigate to that fragment identifier and abort these steps.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#navigate-fragid-step
4.11.4.1 Browser button types
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#browser-button-types
scroll to the fragment identifier
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#scroll-to-the-fragment-identifier
Constructing the form data set. For each element field in controls, in tree order, run the following substeps: If any of the following conditions are met, then skip these substeps for this element: The field element has a datalist element ancestor. The field element is disabled. The field element is a button but it is not submitter. The field element is an input element whose type attribute is in the Checkbox state and whose checkedness is false. The field element is an input element whose type attribute is in the Radio Button state and whose checkedness is false. The field element is an input element whose type attribute is in the File Upload state but the control does not have any files selected. The field element is an object element that is not using a plugin. Otherwise, process field as follows: Let type be the value of the type DOM attribute of field. If the field element is an input element whose type attribute is in the Image Button state, then run these further nested substeps: If the field elementhas an name attribute specified and value is not the empty string, let name be that value followed by a single U+002E FULL STOP (.) character. Otherwise, let name be the empty string. Let namex be the string consisting of the concatenation of name and a single U+0078 LATIN SMALL LETTER X (x) character. Let namey be the string consisting of the concatenation of name and a single U+0079 LATIN SMALL LETTER Y (y) character. The field element is submitter, and before this algorithm was invoked the user indicated a coordinate. Let x be the x-component of the coordindate selected by the user, and let y be the y-component of the coordinate selected by the user. Append an entry in the form data set with the name namex, the value x, and the type type. Append an entry in the form data set with the name namey and the value y, and the type type. Skip the remaining substeps for this element: if there are any more elements in controls, return to the top of the constructing the form data set step, otherwise, jump to the net step in the overall form submission algorithm. If the field element does not have a name attribute specified, or its name attribute's value is the empty string, skip these substeps for this element: if there are any more elements in controls, return to the top of the constructing the form data set step, otherwise, jump to the next step in the overall form submission algorithm. Let name be the value of the field element's name attribute. If the field element is a select element, then for each option element in the select element whose selectedness is true, append an entry in the form data set with the name as the name, the value of the option element as the value, and type as the type. Otherwise, if the field element is an input element whose type attribute is in the Checkbox state or the Radio Button state, then then run these further nested substeps: If the field element has a value attribute specified, then let value be the value of that attribute; otherwise, let value be the string "on". Append an entr in the form data set with name as the name, value as the value, and type as the type. Otherwise, if the field element is an input element whose type attribute is in the File Upload state, then for each file selected in the input element, append an entry in the form data set with the name as the name, the file (consisting of the name, the type, and the body) as the value, and type as the type. Otherwise, if the field element is an object element: try to obtain a form submission value from the plugin, and if that is successful, append an entry in the form data set with name as the name, the returned form submission value as the value, and the string "object" as the type. Otherwise, append an entry in the form data set with name as the name, the value of the field element as the value, and type as the type.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#constructing-form-data-set
3.2.3 Resource metadata management
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#resource-metadata-management
3.2.2 Security
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#security
replace(url)
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#dom-location-replace
Status of this document
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#status-of-this-document
3 Semantics and structure of HTML documents
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#dom
3.2.1 Documents in the DOM
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#documents-in-the-dom
src
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#attr-iframe-src
Non-document content: If, given type, the new resource is to be handled by displaying some sort of inline content, e.g. a native rendering of the content, an error message because the specified type is not supported, or an inline prompt to allow the user to select a registered handler for the given type, then display the inline content and abort these steps.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#navigate-non-Document
lastModified
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#dom-document-lastmodified
XML documents
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#xml-documents
pushState(data, title, url)
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#dom-history-pushstate
Editor's Draft 27 November 2008
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1639.html#editor-s-draft-date-zzz-9-june-2008
http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1638&r2=1.1639&f=h
http://html5.org/tools/web-apps-tracker?from=2467&to=2468
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1638
retrieving revision 1.1639
diff -u -d -r1.1638 -r1.1639
--- Overview.html 26 Nov 2008 23:14:09 -0000 1.1638
+++ Overview.html 27 Nov 2008 02:00:35 -0000 1.1639
@@ -8,7 +8,7 @@
<p><a href=http://www.w3.org/><img alt=W3C height=48 src=http://www.w3.org/Icons/w3c_home width=72></a></p>
<h1>HTML 5</h1>
<h2 class="no-num no-toc" id=a-vocabulary-and-associated-apis-for-html-and-xhtml>A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->26 November 2008</h2>
+ <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->27 November 2008</h2>
<dl><!-- ZZZ: update the month/day
<dt>This Version:</dt>
<dd><a href="http://www.w3.org/TR/2008/WD-html5-20080610/">http://www.w3.org/TR/2008/WD-html5-20080610/</a></dd>
@@ -97,7 +97,7 @@
specification's progress along the W3C Recommendation
track.
<!--ZZZ:-->
- This specification is the 26 November 2008 <!--ZZZ "Working Draft"-->Editor's Draft.
+ This specification is the 27 November 2008 <!--ZZZ "Working Draft"-->Editor's Draft.
<!--:ZZZ-->
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href=http://www.whatwg.org/>WHATWG</a>. The two specifications are
identical from the table of contents onwards.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -3313,20 +3313,20 @@
the <a href=#absolute-url>absolute URL</a> obtained by running these steps:<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
@@ -4665,13 +4665,17 @@
<li value=81><dfn id=parse_err><code>PARSE_ERR</code></dfn></li> <!-- actually defined in dom3ls -->
<li value=82><dfn id=serialise_err><code>SERIALISE_ERR</code></dfn></li> <!-- actually defined in dom3ls -->
</ol><h2 id=dom><span class=secno>3 </span>Semantics and structure of HTML documents</h2><h3 id=semantics-intro><span class=secno>3.1 </span>Introduction</h3><p><em>This section is non-normative.</em><p class=XXX>An introduction to marking up a document.<h3 id=documents><span class=secno>3.2 </span>Documents</h3><p>Every XML and HTML document in an HTML UA is represented by a
- <code>Document</code> object. <a href=#references>[DOM3CORE]</a><h4 id=documents-in-the-dom><span class=secno>3.2.1 </span>Documents in the DOM</h4><p><code>Document</code> objects are assumed to be <dfn id=xml-documents>XML
+ <code>Document</code> object. <a href=#references>[DOM3CORE]</a><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>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><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
documents</dfn> when they are created. Whether a document is an
<a href=#html-documents title="HTML documents">HTML document</a> or an <a href=#xml-documents title="XML documents">XML document</a> affects the behavior of
certain APIs, as well as a few CSS rendering rules. <a href=#references>[CSS21]</a><p class=note>A <code>Document</code> object created by the <code title="">createDocument()</code> API on the
<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>All <code>Document</code> objects (in user agents implementing
+ <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.<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
binding-specific methods. (This is the case whether or not the
@@ -4745,12 +4749,11 @@
accessed by scripts whose <a href=#effective-script-origin>effective script origin</a> is
not the <a href=#same-origin title="same origin">same</a> as the
<code>Document</code>'s <a href=#effective-script-origin>effective script origin</a>.<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>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>
+ attribute must return <a href=#the-document-s-address>the document's address</a>.<p>The <dfn id=dom-document-referrer title=dom-document-referrer><code>referrer</code></dfn> attribute
+ 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
@@ -4766,20 +4769,19 @@
understand it. --><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=#references>[RFC2109]</a> <a href=#references>[RFC2965]</a><p>On setting, if the <a href=#sandboxed-origin-browsing-context-flag>sandboxed origin browsing context
+ <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=#references>[RFC2109]</a> <a href=#references>[RFC2965]</a><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=#references>[RFC2109]</a> <a href=#references>[RFC2965]</a><p class=note>Since the <code title=dom-document-cookie><a href=#dom-document-cookie>cookie</a></code> attribute is accessible
+ 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=#references>[RFC2109]</a> <a href=#references>[RFC2965]</a><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>
@@ -12509,7 +12511,7 @@
browsing context</a>.</p><!-- It doesn't happen when the base
URL is changed, though. --><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 <dfn id=attr-iframe-name title=attr-iframe-name><code>name</code></dfn>
+ the initial <code><a href=#about:blank>about:blank</a></code> page.<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
name</a>. When the browsing context is created, if the attribute
is present, the <a href=#browsing-context-name>browsing context name</a> must be set to
@@ -12680,8 +12682,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:<ul><li><p>The user agent must set the <dfn id=seamless-browsing-context-flag>seamless browsing
context flag</dfn> to true for that <a href=#browsing-context>browsing
@@ -23184,8 +23186,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=#references>[RFC3986]</a></p>
@@ -25351,9 +25352,8 @@
this mode of operation.<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 class=warning>The confirmation is needed because it is
+ 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 class=warning>The confirmation is needed because it is
relatively easy to trick users into activating buttons. The
confirmation could, e.g. take the form of asking the user where to
"save" the application, or non-modal information panel that is
@@ -25992,16 +25992,13 @@
<code>Document</code> is given by the <code title="">defaultView</code> attribute on the <code>Document</code>
object's <code>DocumentView</code> interface. <a href=#references>[DOM3VIEWS]</a><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 id=about-blank-origin>The <a href=#origin-0>origin</a> of the
+ 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 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
<code>Document</code> is created, in a manner dependent on whether
the <a href=#browsing-context>browsing context</a> created is a <a href=#nested-browsing-context>nested browsing
@@ -26380,8 +26377,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>The second argument, <var title="">target</var>, specifies the
<a href=#browsing-context-name title="browsing context name">name</a> of the browsing
context that is to be navigated. It must be a <a href=#valid-browsing-context-name-or-keyword>valid browsing
@@ -26614,8 +26610,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
@@ -26634,8 +26631,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
@@ -29555,9 +29552,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
@@ -29634,7 +29630,7 @@
if it is in a <a href=#browsing-context>browsing context</a>, and null otherwise.<p>The <dfn id=dom-location title=dom-location><code>location</code></dfn>
attribute of the <code><a href=#window>Window</a></code> interface must return the
<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><code><a href=#location>Location</a></code> objects provide a representation of <span title="the document's address">their document's address</span>, and
+ <a href=#active-document>active document</a>.<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>
@@ -29656,10 +29652,9 @@
// resolving relative URLs
DOMString <a href=#dom-location-resolveurl title=dom-location-resolveURL>resolveURL</a>(in DOMString url);
};</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>On setting, <!--XXX Mozilla does this, but IE doesn't. What
+ 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>On setting, <!--XXX Mozilla does this, but IE doesn't. What
should we do?: the behavior depends on the context in which the
script that set the attribute is running. If the script ran as the
direct result of the execution of a <code>script</code> element in
@@ -29695,12 +29690,13 @@
user reload must be equivalent to .reload()
--><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><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
+ 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
that succeeds, return the resulting <a href=#absolute-url>absolute URL</a>. If it
fails, it must throw a <code><a href=#syntax_err>SYNTAX_ERR</a></code> exception
@@ -29779,10 +29775,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>
@@ -29877,11 +29872,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>
@@ -29939,7 +29933,17 @@
<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
@@ -30149,7 +30153,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 ? --><p>Part of that algorithm involves the user agent having to
+ specified fragment identifier.<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
important part for this step.<p>When the user agent is required to <dfn id=scroll-to-the-fragment-identifier>scroll to the fragment
identifier</dfn>, it must change the scrolling position of the
@@ -31197,29 +31201,27 @@
POST method, with an entity body with the MIME type <code title="">text/ping</code> consisting of the four-character string
"<code title="">PING</code>". All relevant cookie and HTTP
authentication headers must be included in the request. Which other
- headers are required depends on the URLs involved.<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>
+ headers are required depends on the URLs involved.<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
Received on Thursday, 27 November 2008 02:04:41 UTC