W3C home > Mailing lists > Public > public-html-commits@w3.org > June 2008

html5/spec Overview.html,1.923,1.924

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 09 Jun 2008 22:32:38 +0000
To: public-html-commits@w3.org
Message-Id: <E1K5puo-0007E3-6E@lionel-hutz.w3.org>

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv27740

Modified Files:
	Overview.html 
Log Message:
put XXXDOCURL markers wherever the term 'the document's address' is present, for easy finding later when i go and define that somehow. (whatwg r1735)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.923
retrieving revision 1.924
diff -u -d -r1.923 -r1.924
--- Overview.html	9 Jun 2008 22:22:34 -0000	1.923
+++ Overview.html	9 Jun 2008 22:32:35 -0000	1.924
@@ -2863,8 +2863,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
@@ -2897,17 +2897,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="#references">[RFC2109]</a>
+   resource indicated by <span>the document's
+   address</span><!-- XXXDOCURL --> over HTTP, as per RFC 2109 section 4.3.4.
+   <a href="#references">[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="#references">[RFC2109]</a>
 
   <p class=note>Since the <code title=dom-document-cookie><a
@@ -28558,9 +28559,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
@@ -29332,8 +29334,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
Received on Monday, 9 June 2008 22:33:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 October 2008 20:32:57 GMT