Re: [whatwg/url] can't parse urls starting with xn-- (#438)

Example: `http://xn--a.xn--nxa/`

According to "ASCII fast path" it must pass. But I can't browse to this address. When entered in the address bar, Chrome converts it to `http://xn--a.β/` and fails (because it treats `http://xn--a.β/` invalid). I think if Chrome converts it to Unicode form, then must treat both equivalent. But actually it isn't:
- `new URL("http://xn--a.xn--nxa/")` - succeeds
- `new URL("http://xn--a.β/")` - throws

I think if URL's ASCII form is valid, then converted to Unicode form must by valid too. And vice versa - if URL is invalid in one form, then it must be invalid in other form too. Otherwise we got weird results. So I am the opposite of "ASCII fast path".


-- 
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/438#issuecomment-702019291