HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
2468Define 'the document's address'.2008-11-27 02:00
@@ -3560,36 +3560,35 @@
 
   <p>The <dfn>document base URL</dfn> of a <code>Document</code> is
   the <span>absolute URL</span> obtained by running these steps:</p>
 
   <ol>
 
    <li><p>If there is no <code>base</code> element that is both a
    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>
 
   <p>To <dfn>resolve a URL</dfn> to an <span>absolute URL</span> the
   user agent must use the following steps. Resolving a URL can result
   in an error, in which case the URL is not resolvable.</p>
 
   <ol>
 
    <li><p>Let <var title="">url</var> be the <span>URL</span> being
@@ -5561,38 +5560,47 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20html%3E..
 
   <p class="XXX">An introduction to marking up a document.</p>
 
 
   <h3>Documents</h3>
 
   <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>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
   documents</dfn> when they are created. Whether a document is an
   <span title="HTML documents">HTML document</span> or an <span
   title="XML documents">XML document</span> affects the behavior of
   certain APIs, as well as a few CSS rendering rules. <a
   href="#refsCSS21">[CSS21]</a></p>
 
   <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 <span
   title="XML documents">XML document</span>, but can be made into an
   <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
   binding-specific methods. (This is the case whether or not the
   document in question is an <span title="HTML documents">HTML
   document</span> or indeed whether it contains any <span>HTML
   elements</span> at all.) <code>Document</code> objects must also
   implement the document-level interface of any other namespaces found
   in the document that the UA supports. For example, if an HTML
   implementation also supports SVG, then the <code>Document</code>
@@ -5670,89 +5678,84 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20html%3E..
   any of the members of an <code>HTMLDocument</code> object are
   accessed by scripts whose <span>effective script origin</span> is
   not the <span title="same origin">same</span> as the
   <code>Document</code>'s <span>effective script origin</span>.</p>
 
 
 
   <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
   referrers in this case, or if the navigation was initiated for a
   <span>hyperlink</span> with a <code
   title="rel-noreferrer">noreferrer</code> keyword.</p>
 
   <p class="note">In the case of HTTP, the <code
   title="dom-document-referrer">referrer</code> DOM attribute will
   match the <code title="">Referer</code> (sic) header that was sent
   when <span title="fetch">fetching</span> the current page.</p>
 
   <p class="note">Typically user agents are configured to not report
   referrers in the case where the referrer uses an encrypted protocol
   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 title="dom-document-cookie"><code>cookie</code></dfn>
   attribute represents the cookies of the resource.</p>
 
   <!-- XXX this needs work; e.g. document.open() should return the
   cookies of the document that called document.open(), not of
   about:blank or the document that had .open() called on, as I
   understand it. -->
 
   <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
   title="dom-document-cookie">cookie</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
   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
   user's local timezone, in the following format:</p>
 
   <ol>
 
@@ -16404,21 +16407,21 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
   <p>Whenever the <code title="attr-iframe-src">src</code> attribute
   is set, the nested <span>browsing context</span> must be <span
   title="navigate">navigated</span> to the <span>URL</span> given by
   that attribute's value, with the <code>iframe</code> element's
   document's <span>browsing context</span> as the <span>source
   browsing context</span>.</p> <!-- It doesn't happen when the base
   URL is changed, though. -->
 
   <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
   name</span>. When the browsing context is created, if the attribute
   is present, the <span>browsing context name</span> must be set to
   the value of this attribute; otherwise, the <span>browsing context
   name</span> must be set to the empty string.</p>
 
   <p>Whenever the <code title="attr-iframe-name">name</code> attribute
   is set, the nested <span>browsing context</span>'s <span
@@ -32372,22 +32375,21 @@ interface <dfn>HTMLOptionElement</dfn> : <span>HTMLElement</span> {
 
    </li>
 
    <li><p>Let <var title="">action</var> be the <var
    title="">submitter</var> element's <span
    title="concept-fs-action">action</span>.</p></li>
 
    <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>
 
     <!-- Don't ask me why. But that's what IE does. It even treats
     action="" differently from action=" " or action="#" (the latter
     two resolve to the base URL, the first one resolves to the doc
     URL). And other browsers concur. It is even required, see e.g.
       http://bugs.webkit.org/show_bug.cgi?id=7763
       https://bugzilla.mozilla.org/show_bug.cgi?id=297761
@@ -35446,22 +35448,21 @@ XXX selection ranges -->
   applications, as if they were not Web sites at all. The <i
   title="attr-bb-type-makeapp-state">make application</i> state exists
   to allow Web pages to offer themselves to the user as targets for
   this mode of operation.</p>
 
   <p>The <i>action</i> of the <i
   title="attr-bb-type-makeapp-state">make application</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>
+  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
   confirmation could, e.g. take the form of asking the user where to
   "save" the application, or non-modal information panel that is
   clearly from the user agent and gives the user the opportunity to
   drag an icon to their system's application launcher.</p>
 
   <p>The <i>relevance</i> of the <i
   title="attr-bb-type-makeapp-state">make application</i> state is
@@ -36536,30 +36537,29 @@ explain that only direct children of the <menu> matter
   interacts with a user agent is the <dfn>default view</dfn>.</p>
 
   <p class="note">The <span>default view</span> of a
   <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="#refsDOM3VIEWS">[DOM3VIEWS]</a></p>
 
   <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
   <code>Document</code> is created, in a manner dependent on whether
   the <span>browsing context</span> created is a <span>nested browsing
   context</span>, as follows:
 
   <dl class="switch">
 
    <dt>If the new <span>browsing context</span> is a <span>nested
@@ -37084,22 +37084,22 @@ explain that only direct children of the <menu> matter
   title="navigate">navigating</span> an existing <span>browsing
   context</span> or opening and navigating an <span>auxiliary browsing
   context</span>.</p>
 
   <p>The method has four arguments, though they are all optional.</p>
 
   <p>The first argument, <var title="">url</var>, must be a
   <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
   <span title="browsing context name">name</span> of the browsing
   context that is to be navigated. It must be a <span>valid browsing
   context name or keyword</span>. If fewer than two arguments are
   provided, then the <var title="">name</var> argument defaults to the
   value "<code>_blank</code>".</p>
 
   <p>The third argument, <var title="">features</var>, has no effect
@@ -37392,22 +37392,23 @@ explain that only direct children of the <menu> matter
      <dd>The <span>origin</span> is equal to the <span>origin</span>
      of the script of that <span title="javascript
      protocol"><code>javascript:</code> URL</span>.</dd>
 
 
      <dt>If a <code>Document</code> or image was served over the
      network and has an address that uses a URL scheme with a
      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
      <code title="">data:</code> URL that was returned as the location
      of an HTTP redirect (or equivalent in other protocols)</dt>
 
      <dd>The <span>origin</span> is the <span>origin</span> of the
      <span>URL</span> that redirected to the <code
      title="">data:</code> URL.</dd>
 
@@ -37415,21 +37416,21 @@ explain that only direct children of the <menu> matter
      <dt>If a <code>Document</code> or image was generated from a
      <code title="">data:</code> URL found in another
      <code>Document</code> or in a script</dt>
 
      <dd>The <span>origin</span> is the <span>origin</span> of the
      <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 -->
+     document's address">address</span>
      "<code>about:blank</code>"</dt>
 
      <dd>The <span>origin</span> of the <code>Document</code> is <a
      href="#about-blank-origin">the <span>origin</span> it was
      assigned when its browsing context was created</a>.</dd>
 
 
      <dt>If a <code>Document</code> or image was obtained in some
      other manner (e.g. a <code title="">data:</code> URL typed in by
      the user, a <code>Document</code> created using the <code
@@ -41411,22 +41412,22 @@ style/default.css</pre>
     <ol>
 
      <li><span title="resolve a url">Resolve</span> the value of the
      third argument.</li>
 
      <li>If that fails, raise a <code>SECURITY_ERR</code> exception and
      abort the <code title="dom-history-pushState">pushState()</code>
      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">&lt;path&gt;</span>, <span
      title="url-query">&lt;query&gt;</span>, and <span
      title="url-fragment">&lt;fragment&gt;</span> components, then
      raise a <code>SECURITY_ERR</code> exception and abort the <code
      title="dom-history-pushState">pushState()</code> steps.</li>
 
     </ol>
 
     <p>For the purposes of the comparison in the above substeps, the
     <span title="url-path">&lt;path&gt;</span> and <span
@@ -41576,23 +41577,22 @@ style/default.css</pre>
            attribute DOMString <span title="dom-location-pathname">pathname</span>;
            attribute DOMString <span title="dom-location-search">search</span>;
            attribute DOMString <span title="dom-location-hash">hash</span>;
 
   // resolving relative URLs
   DOMString <span title="dom-location-resolveURL">resolveURL</span>(in DOMString url);
 };</pre>
 
   <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
   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
   the document represented by the <code>Location</code> object's
   associated <code>Document</code> object, then the user agent must
   act as if the <code title="dom-location-replace">replace()</code>
   method had been called with the new value as its
   argument. Otherwise,--> the user agent must act as if the <code
@@ -41640,27 +41640,27 @@ user reload must be equivalent to .reload()
   <span>URL decomposition attributes</span>, <dfn
   title="dom-location-protocol"><code>protocol</code></dfn>, <dfn
   title="dom-location-host"><code>host</code></dfn>, <dfn
   title="dom-location-port"><code>port</code></dfn>, <dfn
   title="dom-location-hostname"><code>hostname</code></dfn>, <dfn
   title="dom-location-pathname"><code>pathname</code></dfn>, <dfn
   title="dom-location-search"><code>search</code></dfn>, and <dfn
   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>
 
   <p>The <dfn title="dom-location-resolveURL"><code>resolveURL(<var
   title="">url</var>)</code></dfn> method must <span title="resolve a
   url">resolve</span> its <var title="">url</var> argument, and if
   that succeeds, return the resulting <span>absolute URL</span>. If it
   fails, it must throw a <code>SYNTAX_ERR</code> exception
   instead.</p>
 
@@ -41782,24 +41782,23 @@ user reload must be equivalent to .reload()
 
    <li><span title="resolve a url">Resolve</span> the <span>URL</span>
    of the new resource. If that fails, the user agent may abort these
    steps, or may treat the URL as identifying some sort of user-agent
    defined error resource, which could display some sort of inline
    content, or could be handled using a mechanism that does not affect
    the browsing context.</li>
 
    <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">&lt;fragment&gt;</span> components of those
    <span title="URL">URLs</span>, and the new resource is to be
    fetched using HTTP GET or equivalent, then <span
    title="navigate-fragid">navigate to that fragment identifier</span>
    and abort these steps.</p></li>
 
    <li><p>If the new resource is to be handled by displaying some sort
    of inline content, e.g. an error message because the specified
    scheme is not one of the supported protocols, or an inline prompt
    to allow the user to select <span
@@ -41892,25 +41891,24 @@ user reload must be equivalent to .reload()
     title="concept-appcache-foreign">foreign</span>, then the user
     agent must discard the failed load and instead continue along
     these steps using <var title="">candidate</var> as the
     resource.</p>
 
     <p>For the purposes of session history (and features that depend
     on session history, e.g. bookmarking) the user agent must use the
     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>
 
    <li><p>If the document's out-of-band metadata (e.g. HTTP headers),
    not counting any <span title="Content-Type">type information</span>
    (such as the Content-Type HTTP header), requires some sort of
    processing that will not affect the browsing context, then perform
    that processing and abort these steps.</p>
 
    <div class="note">
@@ -41964,20 +41962,32 @@ user reload must be equivalent to .reload()
      steps.</dd>
 
      <dt>A type that will use an external application to render the
      content in the <span>browsing context</span></dt>
      <dd>Follow the steps given in the <span
      title="navigate-plugin">plugin</span> section, and abort these
      steps.</dd>
 
     </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,
    given <var title="">type</var>, 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 <span
    title="dom-navigator-registerContentHandler">a registered
    handler</span> for the given type, then <span
    title="navigate-ua-inline">display the inline content</span> and
@@ -42317,21 +42327,21 @@ user reload must be equivalent to .reload()
   <span>update the session history with the new page</span>.</p>
 
 
 
   <h4 id="scroll-to-fragid"><dfn title="navigate-fragid">Navigating to a fragment identifier</dfn></h4>
 
   <p>When a user agent is supposed to navigate to a fragment
   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
   important part for this step.</p>
 
   <p>When the user agent is required to <dfn>scroll to the fragment
   identifier</dfn>, it must change the scrolling position of the
   document, or perform some other action, such that <span>the
   indicated part of the document</span> is brought to the user's
   attention. If there is no indicated part, then the user agent must
@@ -43938,43 +43948,42 @@ interface <dfn>SQLStatementErrorCallback</dfn> {
   <p>For URLs that are HTTP URLs, the requests must be performed by
   <span title="fetch">fetching</span> the specified URLs using the
   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.</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 <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
    encrypted connection</dt>
 
    <dd>The request must include a <code title="">Ping-To</code> HTTP
    header with, as its value, the address of the target of the
    hyperlink. The request must neither include a <code
    title="">Referer</code> HTTP header nor include a <code
    title="">Ping-From</code> HTTP header.</dd>

|