Non-special schema URL behaviors differently...

[shrinktofit]

Given new URL("db://x/y/z").

Chrome, Firefox, Edge:

pathname: "//x/y/z",

NodeJS:

hostname: 'x',
pathname: '/y/z',

---

Given new URL("file:x/y/z").

Chrome, Edge:

host: "x"
pathname: "/y/z"

Firefox, NodeJS:

pathname: "/x/y/z"

[achristensen07]

With the first example, Safari and NodeJS follow the spec and Chrome ant Firefox have told me of their intent to change to follow the spec.

I’d have to look more closely at the second example with a laptop.

[annevk]

(Aside: file URLs are special URLs. This might be #405.)

[domenic]

Given that the first is working as intended, and #405 got fixed, I think this is probably closeable. In particular, for the second case, the spec matches Firefox and Safari (2/3 engines).

/cc @alwinb