Re: [whatwg/url] Need an "unreserved" character set (and better define how to percent-encode arbitrary strings) (#369) from Matt Giuca on 2018-04-12 (public-webapps-github@w3.org from April 2018)

From: Matt Giuca <notifications@github.com>
Date: Thu, 12 Apr 2018 03:24:44 +0000 (UTC)
To: whatwg/url <url@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/url/issues/369/380665385@github.com>

I agree with @LEW21. By making the reserved set match RFC 2396, we would be undoing the change of the newer RFC, but I believe that would align with the WHATWG mission of describing things as they are, not how they "should be". Most software that I've seen matches RFC 2396, including common programming language libraries.

(Of course, there will be software that follows RFC 3986 also. It's a tough decision.)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/369#issuecomment-380665385

Received on Thursday, 12 April 2018 03:25:08 UTC