Re: [whatwg/url] Allow `//` when base exists (#553)

Right, that's the current spec's behavior. What the original test case tries to handle `//` as is a path-relative-URL instead. That is not valid at the moment, but it tries to reproduce `http://localhost:3000//`. The only way we can do that is to make it a clear relative path with a dot like the below:

```js
new (URL('/.//', 'http://localhost:3000).href

// => "http://localhost:3000//"
```

I'm wondering if it's worth letting `scheme-relative-special-URL string` ignore the provided item only when it's an empty host `//` and leverage `path-relative-URL` to handle`//` which is what the original issue reporter expected.

-- 
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/553#issuecomment-706652859