[] (1) Mention that relative URIs must be resolved in pushState(). We…

… don't yet say how. Resolving URIs in script arguments are a wider issue.

git-svn-id: http://svn.whatwg.org/webapps@993 340c8d12-0b0e-0410-8428-c7bf67bfef74

index

@@ -23534,15 +23534,15 @@ XXX selection ranges -->
   <p>When this method is invoked, the user agent must first check the third
    argument. If a third argument is specified, then the user agent must
    verify that the third argument is a valid URI or IRI (as defined by RFC
-   3986 and 3987, and as modified by RFC 2732), and if so, that the URI or
-   IRI is either identical to the document's URI, or that it differs from the
-   document's URI only in the &lt;query&gt;, &lt;abs_path&gt;, and/or
-   &lt;fragment&gt; parts, as applicable (the &lt;query&gt; and
-   &lt;abs_path&gt; parts can only be the same if the document's URI uses a
-   hierarchical &lt;scheme&gt;). If the verification fails (either because
-   the argument is syntactically incorrect, or differs in a way not described
-   as acceptable in the previous sentence) then the user agent must raise a
-   <a href="#security8">security exception</a>. <a
+   3986 and 3987, and as modified by RFC 2732), and if so, that, after
+   resolving it to an absolute URI, it is either identical to the document's
+   URI, or that it differs from the document's URI only in the &lt;query&gt;,
+   &lt;abs_path&gt;, and/or &lt;fragment&gt; parts, as applicable (the
+   &lt;query&gt; and &lt;abs_path&gt; parts can only be the same if the
+   document's URI uses a hierarchical &lt;scheme&gt;). If the verification
+   fails (either because the argument is syntactically incorrect, or differs
+   in a way not described as acceptable in the previous sentence) then the
+   user agent must raise a <a href="#security8">security exception</a>. <a
    href="#refsRFC3986">[RFC3986]</a> <a href="#refsRFC3987">[RFC3987]</a> <a
    href="#refsRFC2732">[RFC2732]</a>
 

source

@@ -21141,15 +21141,15 @@ XXX selection ranges -->
   third argument. If a third argument is specified, then the user
   agent must verify that the third argument is a valid URI or IRI (as
   defined by RFC 3986 and 3987, and as modified by RFC 2732), and if
-  so, that the URI or IRI is either identical to the document's URI,
-  or that it differs from the document's URI only in the
-  <query>, <abs_path>, and/or <fragment> parts, as
-  applicable (the <query> and <abs_path> parts can only be
-  the same if the document's URI uses a hierarchical
-  <scheme>). If the verification fails (either because the
-  argument is syntactically incorrect, or differs in a way not
-  described as acceptable in the previous sentence) then the user
-  agent must raise a <span>security exception</span>. <a
+  so, that, after resolving it to an absolute URI, it is either
+  identical to the document's URI, or that it differs from the
+  document's URI only in the &lt;query&gt;, &lt;abs_path&gt;, and/or
+  &lt;fragment&gt; parts, as applicable (the &lt;query&gt; and
+  &lt;abs_path&gt; parts can only be the same if the document's URI
+  uses a hierarchical &lt;scheme&gt;). If the verification fails
+  (either because the argument is syntactically incorrect, or differs
+  in a way not described as acceptable in the previous sentence) then
+  the user agent must raise a <span>security exception</span>. <a
   href="#refsRFC3986">[RFC3986]</a> <a
   href="#refsRFC3987">[RFC3987]</a> <a
   href="#refsRFC2732">[RFC2732]</a></p>