[html5] r1735 - /

whatwg at whatwg.org whatwg at whatwg.org
Mon Jun 9 15:32:31 PDT 2008


Author: ianh
Date: 2008-06-09 15:32:31 -0700 (Mon, 09 Jun 2008)
New Revision: 1735

Modified:
   index
   source
Log:
[e] (0) put XXXDOCURL markers wherever the term 'the document's address' is present, for easy finding later when i go and define that somehow.

Modified: index
===================================================================
--- index	2008-06-09 22:22:29 UTC (rev 1734)
+++ index	2008-06-09 22:32:31 UTC (rev 1735)
@@ -2772,8 +2772,8 @@
    metadata management</dfn></h4>
 
   <p>The <dfn id=url title=dom-document-URL><code>URL</code></dfn> attribute
-   must return <span>the document's address</span><!-- XXX
-  xref -->.
+   must return <span>the document's address</span><!--
+  XXXDOCURL xref -->.
 
   <p>The <dfn id=referrer
    title=dom-document-referrer><code>referrer</code></dfn> attribute must
@@ -2806,17 +2806,18 @@
    must raise a <a href="#security9">security exception</a>. Otherwise, it
    must return the same string as the value of the <code
    title="">Cookie</code> HTTP header it would include if fetching the
-   resource indicated by <span>the document's address</span> over HTTP, as
-   per RFC 2109 section 4.3.4. <a href="#refsRFC2109">[RFC2109]</a>
+   resource indicated by <span>the document's
+   address</span><!-- XXXDOCURL --> over HTTP, as per RFC 2109 section 4.3.4.
+   <a href="#refsRFC2109">[RFC2109]</a>
 
   <p>On setting, if the <a href="#sandboxed2">sandboxed origin browsing
    context flag</a> is set on the <a href="#browsing1">browsing context</a>
    of the document, the user agent must raise a <a href="#security9">security
    exception</a>. Otherwise, the user agent must act as it would when
    processing cookies if it had just attempted to fetch <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. <a
+   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. <a
    href="#refsRFC2109">[RFC2109]</a>
 
   <p class=note>Since the <code title=dom-document-cookie><a
@@ -28467,9 +28468,10 @@
 
   <p>When a <a href="#browsing1">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> is
-   <code>about:blank</code><!-- XXX xref -->, which is marked as being an <a
-   href="#html-" title="HTML documents">HTML document</a>, and whose <a
+   history, whose <span title="the document's address">address</span><!--
+  XXXDOCURL -->
+   is <code>about:blank</code><!-- XXX xref -->, which is marked as being an
+   <a href="#html-" title="HTML documents">HTML document</a>, and whose <a
    href="#character1" title="document's character encoding">character
    encoding</a> is UTF-8. The <code>Document</code> must have a single child
    <code><a href="#html">html</a></code> node, which itself has a single
@@ -29241,8 +29243,10 @@
       authority
 
      <dd>The <a href="#origin0">origin</a> is the <a
-      href="#origin0">origin</a> of the full URI of the <code>Document</code>
-      or image.
+      href="#origin0">origin</a> of the <span title="the document's
+      address">full URI</span><!--
+     XXXDOCURL --> of the
+      <code>Document</code> or image.
 
      <dt>If a <code>Document</code> or image was generated from a <code
       title="">data:</code> URI that was returned as the location of an HTTP

Modified: source
===================================================================
--- source	2008-06-09 22:22:29 UTC (rev 1734)
+++ source	2008-06-09 22:32:31 UTC (rev 1735)
@@ -1034,8 +1034,8 @@
   <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><!-- XXX
-  xref -->.</p>
+  attribute must return <span>the document's address</span><!--
+  XXXDOCURL xref -->.</p>
 
 
   <p>The <dfn
@@ -1071,18 +1071,18 @@
   <span>security exception</span>. Otherwise, it must return the same
   string as the value of the <code title="">Cookie</code> HTTP header
   it would include if fetching the resource indicated by <span>the
-  document's address</span> over HTTP, as per RFC 2109 section
-  4.3.4. <a href="#refsRFC2109">[RFC2109]</a></p>
+  document's address</span><!-- XXXDOCURL --> over HTTP, as per RFC
+  2109 section 4.3.4. <a href="#refsRFC2109">[RFC2109]</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 <span>security
   exception</span>. Otherwise, the user agent must act as it would
   when processing cookies if it had just attempted to fetch <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. <a
-  href="#refsRFC2109">[RFC2109]</a></p>
+  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. <a href="#refsRFC2109">[RFC2109]</a></p>
 
   <p class="note">Since the <code
   title="dom-document-cookie">cookie</code> attribute is accessible
@@ -26154,15 +26154,16 @@
 
   <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> 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><!--
+  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>
 
   <p id="about-blank-origin">The <span>origin</span> of the
   <code>about:blank</code> <code>Document</code> is set when the
@@ -26968,7 +26969,8 @@
      server-based naming authority</dt>
 
      <dd>The <span>origin</span> is the <span>origin</span> of the
-     full URI of the <code>Document</code> or image.</dd>
+     <span title="the document's address">full URI</span><!--
+     XXXDOCURL --> of the <code>Document</code> or image.</dd>
 
 
      <dt>If a <code>Document</code> or image was generated from a




More information about the Commit-Watchers mailing list