- From: Timothy Gu <notifications@github.com>
- Date: Sat, 22 May 2021 01:05:46 -0700
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 22 May 2021 08:05:59 UTC
Interestingly, Chrome actually doesn't treat `file` URLs differently from `http`/`https`. That is, it allows _both_ percent-encoding _and_ IDNs in URLs: ```js new URL('file://félicit ations.fr/test.txt').href // ⇒ file://xn--flicit%20ations-bnb.fr/test.txt new URL('https://exam ple.com').href // ⇒ https://exa%20mple.com/ ``` That's certainly one way around giving file URLs special handling, but no one other than Chrome seems to support this… -- 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/599#issuecomment-846372280
Received on Saturday, 22 May 2021 08:05:59 UTC