Re: [whatwg/url] "The fragment percent-encode set is the C0 contr..." (#378)

One of the [Goals](https://url.spec.whatwg.org/#goals) of the URL Standard is to

> * Align RFC 3986 and RFC 3987 with contemporary implementations and obsolete them in the process. (E.g., spaces, other "illegal" code points, query encoding, equality, canonicalization, are all concepts not entirely shared, or defined.) URL parsing needs to become as solid as HTML parsing. [[RFC3986]](https://url.spec.whatwg.org/#biblio-rfc3986) [[RFC3987]](https://url.spec.whatwg.org/#biblio-rfc3987)

I'm not sure if this is something we want to align with the RFC, but from past experiences there are probably some good reasons why the spec is as it currently is.

Also, Chrome is known to be lagging behind a lot of changes in the URL Standard. In this case it doesn't seem to matter, but otherwise it would be good to test with the [unofficial reference implementation](https://github.com/jsdom/whatwg-url).

-- 
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/378#issuecomment-379932638