[html5] r5214 - [e] (0) sync with http-state

[whatwg at whatwg.org]

Author: ianh
Date: 2010-07-27 21:09:32 -0700 (Tue, 27 Jul 2010)
New Revision: 5214

Modified:
   complete.html
   index
   source
Log:
[e] (0) sync with http-state

Modified: complete.html
===================================================================
--- complete.html	2010-07-28 00:01:15 UTC (rev 5213)
+++ complete.html	2010-07-28 04:09:32 UTC (rev 5214)
@@ -8082,7 +8082,9 @@
   <code><a href=#security_err>SECURITY_ERR</a></code> exception. Otherwise, the user agent must
   first <a href=#obtain-the-storage-mutex>obtain the storage mutex</a> and then return the
   cookie-string for <a href="#the-document's-address">the document's address</a> for a
-  "non-HTTP" API. <a href=#refsCOOKIES>[COOKIES]</a></p>
+  "non-HTTP" API, decoded as UTF-8, with bytes or sequences of bytes
+  that are not valid UTF-8 sequences interpreted as U+FFFD REPLACEMENT
+  CHARACTERs. <a href=#refsCOOKIES>[COOKIES]</a> <a href=#refsRFC3629>[RFC3629]</a></p>
 
   <p>On setting, if the document is a <a href=#cookie-free-document-object>cookie-free
   <code>Document</code> object</a>, then the user agent must do
@@ -8093,7 +8095,7 @@
   as it would when <span title="receives a
   set-cookie-string">receiving a set-cookie-string</span> for
   <a href="#the-document's-address">the document's address</a> via a "non-HTTP" API, consisting
-  of the new value. <a href=#refsCOOKIES>[COOKIES]</a></p>
+  of the new value encoded as UTF-8. <a href=#refsCOOKIES>[COOKIES]</a> <a href=#refsRFC3629>[RFC3629]</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

Modified: index
===================================================================
--- index	2010-07-28 00:01:15 UTC (rev 5213)
+++ index	2010-07-28 04:09:32 UTC (rev 5214)
@@ -8006,7 +8006,9 @@
   <code><a href=#security_err>SECURITY_ERR</a></code> exception. Otherwise, the user agent must
   first <a href=#obtain-the-storage-mutex>obtain the storage mutex</a> and then return the
   cookie-string for <a href="#the-document's-address">the document's address</a> for a
-  "non-HTTP" API. <a href=#refsCOOKIES>[COOKIES]</a></p>
+  "non-HTTP" API, decoded as UTF-8, with bytes or sequences of bytes
+  that are not valid UTF-8 sequences interpreted as U+FFFD REPLACEMENT
+  CHARACTERs. <a href=#refsCOOKIES>[COOKIES]</a> <a href=#refsRFC3629>[RFC3629]</a></p>
 
   <p>On setting, if the document is a <a href=#cookie-free-document-object>cookie-free
   <code>Document</code> object</a>, then the user agent must do
@@ -8017,7 +8019,7 @@
   as it would when <span title="receives a
   set-cookie-string">receiving a set-cookie-string</span> for
   <a href="#the-document's-address">the document's address</a> via a "non-HTTP" API, consisting
-  of the new value. <a href=#refsCOOKIES>[COOKIES]</a></p>
+  of the new value encoded as UTF-8. <a href=#refsCOOKIES>[COOKIES]</a> <a href=#refsRFC3629>[RFC3629]</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
@@ -87512,6 +87514,10 @@
    <dd><cite><a href=http://www.ietf.org/rfc/rfc3548.txt>The Base16, Base32,
    and Base64 Data Encodings</a></cite>, S. Josefsson. IETF.</dd>
 
+   <dt id=refsRFC3629>[RFC3629]</dt>
+   <dd><cite><a href=http://www.ietf.org/rfc/rfc3629.txt>UTF-8, a
+   transformation format of ISO 10646</a></cite>, F. Yergeau. IETF.</dd>
+
    <dt id=refsRFC3864>[RFC3864]</dt>
    <dd><cite><a href=http://www.ietf.org/rfc/rfc3864.txt>Registration Procedures
    for Message Header Fields</a></cite>, G. Klyne, M. Nottingham,

Modified: source
===================================================================
--- source	2010-07-28 00:01:15 UTC (rev 5213)
+++ source	2010-07-28 04:09:32 UTC (rev 5214)
@@ -7926,7 +7926,10 @@
   <code>SECURITY_ERR</code> exception. Otherwise, the user agent must
   first <span>obtain the storage mutex</span> and then return the
   cookie-string for <span>the document's address</span> for a
-  "non-HTTP" API. <a href="#refsCOOKIES">[COOKIES]</a></p>
+  "non-HTTP" API, decoded as UTF-8, with bytes or sequences of bytes
+  that are not valid UTF-8 sequences interpreted as U+FFFD REPLACEMENT
+  CHARACTERs. <a href="#refsCOOKIES">[COOKIES]</a> <a
+  href="#refsRFC3629">[RFC3629]</a></p>
 
   <p>On setting, if the document is a <span>cookie-free
   <code>Document</code> object</span>, then the user agent must do
@@ -7937,7 +7940,8 @@
   as it would when <span title="receives a
   set-cookie-string">receiving a set-cookie-string</span> for
   <span>the document's address</span> via a "non-HTTP" API, consisting
-  of the new value. <a href="#refsCOOKIES">[COOKIES]</a></p>
+  of the new value encoded as UTF-8. <a
+  href="#refsCOOKIES">[COOKIES]</a> <a href="#refsRFC3629">[RFC3629]</a></p>
 
   <p class="note">Since the <code
   title="dom-document-cookie">cookie</code> attribute is accessible