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

@LEW21 I had another look. 

* Encoding `^` for paths is still a reasonable suggestion as Chrome and Firefox both do encode it, but since Safari matches the specification and nobody else made an attempt it seems somewhat unfair to them to change this now and I'm not sure it's much better. @achristensen07 thoughts?
* What is encoded in fragments changed in 7a3c69f8a1583b33e730c3fea85141a618e7c697 and both Chrome and Firefox seem to align with that. Safari does not (yet) encode ``` ` ``` however.
* `\` in paths means `/` for special URLs per the specification and in most implementations.
* I don't think we should change what is valid as per earlier statements.

-- 
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-623461178

Received on Monday, 4 May 2020 13:23:53 UTC