Re: [whatwg/url] Parser generates invalid URLs (#379)

I've added a number of test cases to test the distinct percent encode sets. The PR (for wpt) is [here][1]. 

Some observations, 

- Safari complies in all but the fragment cases. It does not encode additional characters in the fragment. 
- It seems that Firefox and Chrome do not encode additional characters in the username, password, path, query and fragment of non-special URLs.

Firefox and Chrome deviate from the spec in the following:

- Firefox and Chrome also encode `^` in the path of special URLs. Chrome also encodes `|`. 
- Firefox and Chrome also encode `'` and in the username and password (of special URLs) and Firefox also encodes `.`.
- However Firefox does not encode `|` in the password, in contrast with the spec. 

It's easy to make mistakes with this, so additional eyes would be good. 

[1]: https://github.com/web-platform-tests/wpt/pull/27742

-- 
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/379#issuecomment-784315088