[html5] r1835 - [ct] (2) Don't escape '%' when doing URL resolution. (bug 5802) (credit: hs)
whatwg at whatwg.org
whatwg at whatwg.org
Mon Jun 30 16:52:11 PDT 2008
Author: ianh
Date: 2008-06-30 16:52:10 -0700 (Mon, 30 Jun 2008)
New Revision: 1835
Modified:
index
source
Log:
[ct] (2) Don't escape '%' when doing URL resolution. (bug 5802) (credit: hs)
Modified: index
===================================================================
--- index 2008-06-30 23:44:32 UTC (rev 1834)
+++ index 2008-06-30 23:52:10 UTC (rev 1835)
@@ -2962,8 +2962,9 @@
<p>If parsing <var title="">url</var> resulted in a <a href="#ltpathgt"
title=url-path><path></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 <path> 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 <path> 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☺c%FFd/?e</code>", then the <a
+ title="">//example.com/a^b☺c%FFd%z/?e</code>", then the <a
href="#ltpathgt" title=url-path><path></a> component's substring
- would be "<code title="">/a^b☺c%FFd/</code>" and the two
+ would be "<code title="">/a^b☺c%FFd%z/</code>" and the two
characters that would have to be escaped would be "<code
title="">^</code>" and "<code title="">☺</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><query></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 <query> 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 <query> production
+ defined in RFC 3986:</p>
<ol>
<li>If the character in question cannot be expressed in the encoding
Modified: source
===================================================================
--- source 2008-06-30 23:44:32 UTC (rev 1834)
+++ source 2008-06-30 23:52:10 UTC (rev 1835)
@@ -1228,9 +1228,9 @@
<p>If parsing <var title="">url</var> resulted in a <span
title="url-path"><path></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 <path> 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
+ <path> 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☺c%FFd/?e</code>", then the
+ title="">//example.com/a^b☺c%FFd%z/?e</code>", then the
<span title="url-path"><path></span> component's substring
- would be "<code title="">/a^b☺c%FFd/</code>" and the two
+ would be "<code title="">/a^b☺c%FFd%z/</code>" and the two
characters that would have to be escaped would be "<code
title="">^</code>" and "<code title="">☺</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"><query></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 <query> 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
+ <query> production defined in RFC 3986:</p>
<ol>
More information about the Commit-Watchers
mailing list