[ct] (2) Don't escape '%' when doing URL resolution. (bug 5802) (cred…

…it: hs) git-svn-id: http://svn.whatwg.org/webapps@1835 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jun 30, 2008 · 576b26c · 576b26c
1 parent 09f5e4f
commit 576b26c
Show file tree

Hide file tree

Showing 2 changed files with 18 additions and 16 deletions.
diff --git a/index b/index
@@ -2962,8 +2962,9 @@
     <p>If parsing <var title="">url</var> resulted in a <a href="#ltpathgt"
      title=url-path>&lt;path&gt;</a> component, then replace the matching
      substring of <var title="">url</var> with the string that results from
-     applying the following steps to each character that doesn't match the
-     original &lt;path&gt; production defined in RFC 3986:</p>
+     applying the following steps to each character other than U+0025 PERCENT
+     SIGN (%) that doesn't match the original &lt;path&gt; production defined
+     in RFC 3986:</p>
 
     <ol>
      <li>Encode the character into a sequence of octets as defined by UTF-8.
@@ -2974,22 +2975,23 @@
 
     <div class=example>
      <p>For instance if <var title="">url</var> was "<code
-      title="">//example.com/a^b&#x263a;c%FFd/?e</code>", then the <a
+      title="">//example.com/a^b&#x263a;c%FFd%z/?e</code>", then the <a
       href="#ltpathgt" title=url-path>&lt;path&gt;</a> component's substring
-      would be "<code title="">/a^b&#x263a;c%FFd/</code>" and the two
+      would be "<code title="">/a^b&#x263a;c%FFd%z/</code>" and the two
       characters that would have to be escaped would be "<code
       title="">^</code>" and "<code title="">&#x263a;</code>". The result
       after this step was applied would therefore be that <var
       title="">url</var> now had the value "<code
-      title="">//example.com/a%5Eb%E2%98%BAc%FFd/?e</code>".</p>
+      title="">//example.com/a%5Eb%E2%98%BAc%FFd%z/?e</code>".</p>
     </div>
 
    <li>
     <p>If parsing <var title="">url</var> resulted in a <a href="#ltquerygt"
      title=url-query>&lt;query&gt;</a> component, then replace the matching
      substring of <var title="">url</var> with the string that results from
-     applying the following steps to each character that doesn't match the
-     original &lt;query&gt; production defined in RFC 3986:</p>
+     applying the following steps to each character other than U+0025 PERCENT
+     SIGN (%) that doesn't match the original &lt;query&gt; production
+     defined in RFC 3986:</p>
 
     <ol>
      <li>If the character in question cannot be expressed in the encoding

diff --git a/source b/source
@@ -1228,9 +1228,9 @@
     <p>If parsing <var title="">url</var> resulted in a <span
     title="url-path">&lt;path&gt;</span> component, then replace the
     matching substring of <var title="">url</var> with the string that
-    results from applying the following steps to each character that
-    doesn't match the original &lt;path&gt; production defined in RFC
-    3986:</p>
+    results from applying the following steps to each character other
+    than U+0025 PERCENT SIGN (%) that doesn't match the original
+    &lt;path&gt; production defined in RFC 3986:</p>
 
     <ol>
 
@@ -1245,14 +1245,14 @@
     <div class="example">
 
      <p>For instance if <var title="">url</var> was "<code
-     title="">//example.com/a^b&#x263a;c%FFd/?e</code>", then the
+     title="">//example.com/a^b&#x263a;c%FFd%z/?e</code>", then the
      <span title="url-path">&lt;path&gt;</span> component's substring
-     would be "<code title="">/a^b&#x263a;c%FFd/</code>" and the two
+     would be "<code title="">/a^b&#x263a;c%FFd%z/</code>" and the two
      characters that would have to be escaped would be "<code
      title="">^</code>" and "<code title="">&#x263a;</code>". The
      result after this step was applied would therefore be that <var
      title="">url</var> now had the value "<code
-     title="">//example.com/a%5Eb%E2%98%BAc%FFd/?e</code>".</p>
+     title="">//example.com/a%5Eb%E2%98%BAc%FFd%z/?e</code>".</p>
 
     </div>
 
@@ -1263,9 +1263,9 @@
     <p>If parsing <var title="">url</var> resulted in a <span
     title="url-query">&lt;query&gt;</span> component, then replace the
     matching substring of <var title="">url</var> with the string that
-    results from applying the following steps to each character that
-    doesn't match the original &lt;query&gt; production defined in RFC
-    3986:</p>
+    results from applying the following steps to each character other
+    than U+0025 PERCENT SIGN (%) that doesn't match the original
+    &lt;query&gt; production defined in RFC 3986:</p>
 
     <ol>