From fd97ea10b8c0727ddb451dd23e6f5b764b5f43b8 Mon Sep 17 00:00:00 2001
From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 28 Oct 2016 13:46:47 +0200
Subject: [PATCH] Stop decoding all %2e's in paths
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This basically reverts bee5ad8041adfe6fc676c527bbc3f3cf4562ef67 as it
did not end up shipping in Firefox and the tentative conclusion is that
percent-decoding in URLs while parsing creates more trouble than it’s
worth.

We’ll still handle %2e when it’s part of a single-dot or double-dot
path segment.

Tests: https://github.com/w3c/web-platform-tests/pull/4104.

Closes #87.
---
 url.bs | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/url.bs b/url.bs
index 88845f18..da386b4e 100644
--- a/url.bs
+++ b/url.bs
@@ -1900,12 +1900,8 @@ string <var>input</var>, optionally with a <a>base URL</a> <var>base</var>, opti
        <li><p>If <a>c</a> is "<code>%</code>" and <a>remaining</a> does
        not start with two <a>ASCII hex digits</a>, <a>syntax violation</a>.
 
-       <li><p>If <a>c</a> is "<code>%</code>" and <a>remaining</a>, <a>ASCII lowercased</a> starts
-       with "<code>2e</code>", append "<code>.</code>" to <var>buffer</var> and increase
-       <var>pointer</var> by two.
-
-       <li><p>Otherwise, <a>UTF-8 percent encode</a> <a>c</a> using the <a>default encode set</a>,
-       and append the result to <var>buffer</var>.
+       <li><p><a>UTF-8 percent encode</a> <a>c</a> using the <a>default encode set</a>, and append
+       the result to <var>buffer</var>.
       </ol>
     </ol>