- From: Alwin Blok <notifications@github.com>
- Date: Wed, 16 Jun 2021 02:47:47 -0700
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 16 June 2021 09:48:53 UTC
Thank you, this is useful information. I think I made mistakes reading the standard, so there are mistakes in my question (I think...). My expectation is that three slashes followed by a `c:` _or_ a `c|` style drive letter are valid, e.g. `file:///c:` and `file:///c|` and alike. (But not zero, one or two slashes, though tolerated; in line with the other special URLs). > I don't think it's worth trying too hard to disambiguate drive letters from path components that look like drive letters. There are obviously some trade-offs that need to be accepted when trying to represent both Windows and POSIX paths in a single format. I am interested in this, mostly because it is exactly what I am trying to do... So I should try to understand your point. The thing is, drive letters act differently from path components when resolving URLs, so I would not know a way around it. -- 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/612#issuecomment-862216401
Received on Wednesday, 16 June 2021 09:48:53 UTC