- From: Alwin Blok <notifications@github.com>
- Date: Thu, 24 Sep 2020 01:47:45 -0700
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 24 September 2020 08:47:57 UTC
Hmm. This is actually about a separate issue – the handling of `C|` style drive letters. Apparently, Chrome and Firefox do not handle the `C|` style drive letters according to the standard (they interpret it as an ordinary path component). What is interesting is that IE/Edge prior to version 18 also did not interpret `C|` as a drive letter in a lot of cases. I discovered that whilst making browsershots for this issue and for #302. I just checked. I have no data on e.g. `file:C|`, `file:/C|` and `file://C|`, nor `file://host/C|`, But - `c|/dir/abc` against `file:///` gave `file:///c%7C/dir/abc`. - `file:///c|/dir/abc` did result in `file:///c:/dir/abc`. This has changed since version 18, which does interpret `c|` as a drive letter. As an aside, Safari fails the mentioned tests because it (sometimes? or always?) does not copy the host from the base URL when parsing host-less URLs. I suspect that this is not intentional; it seems inconsistent with the way in which it parses absolute file URLs. It does however handle the `C|` style drive letters according to the standard. -- 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/405#issuecomment-698208289
Received on Thursday, 24 September 2020 08:47:57 UTC