spec/Overview.html 1.2021 2850 Tweak document.domain to handle IPv6 add

Tweak document.domain to handle IPv6 addresses. (whatwg r2850)

5.4.1 Relaxing the same-origin restriction
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2021.html#relaxing-the-same-origin-restriction

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2020&r2=1.2021&f=h
http://html5.org/tools/web-apps-tracker?from=2849&to=2850

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2020
retrieving revision 1.2021
diff -u -d -r1.2020 -r1.2021
--- Overview.html 23 Feb 2009 07:19:56 -0000 1.2020
+++ Overview.html 23 Feb 2009 07:56:28 -0000 1.2021
@@ -29235,11 +29235,12 @@
   </ol><h4 id=relaxing-the-same-origin-restriction><span class=secno>5.4.1 </span>Relaxing the same-origin restriction</h4><p>The <dfn id=dom-document-domain title=dom-document-domain><code>domain</code></dfn>
   attribute on <code>Document</code> objects must be initialized to
   <a href=#the-document-s-domain>the document's domain</a>, if it has one, and the empty
-  string otherwise. On getting, the attribute must return its current
+  string otherwise. If the value is an IPv6 address, then the square
+  brackets from the host portion of the <a href=#url-host title=url-host>&lt;host&gt;</a> component must be omitted from
+  the attribute's value.<p>On getting, the attribute must return its current
   value, unless the document was created by
   <code>XMLHttpRequest</code>, in which case it must throw an
-  <code><a href=#invalid_access_err>INVALID_ACCESS_ERR</a></code> exception. On setting, the user
-  agent must run the following algorithm:<ol><li>
+  <code><a href=#invalid_access_err>INVALID_ACCESS_ERR</a></code> exception.<p>On setting, the user agent must run the following algorithm:<ol><li>
 
     <p>If the document was created by <code>XMLHttpRequest</code>,
     throw an <code><a href=#invalid_access_err>INVALID_ACCESS_ERR</a></code> exception and abort these
@@ -29249,9 +29250,11 @@
 
    <li>
 
-    <p>Apply the IDNA ToASCII algorithm to the new value, with both
-    the AllowUnassigned and UseSTD3ASCIIRules flags set. Let <var title="">new value</var> be the result of the ToASCII
-    algorithm.</p>
+    <p>If the new value is an IP address, let <var title="">new
+    value</var> be the new value. Otherwise, apply the IDNA ToASCII
+    algorithm to the new value, with both the AllowUnassigned and
+    UseSTD3ASCIIRules flags set, and let <var title="">new value</var>
+    be the result of the ToASCII algorithm.</p>
 
     <p>If ToASCII fails to convert one of the components of the
     string, e.g. because it is too long or because it contains invalid
@@ -29268,8 +29271,8 @@
 
     <ol><li>
 
-      <p>If the current value is an IP address, throw a <code><a href=#security_err>SECURITY_ERR</a></code>
-      exception and abort these steps.</p>
+      <p>If the current value is an IP address, throw a
+      <code><a href=#security_err>SECURITY_ERR</a></code> exception and abort these steps.</p>
 
      </li>

Received on Monday, 23 February 2009 08:00:02 UTC