URL: file: URLs have implementation-defined origins

[annevk]

See whatwg/url#780 for context.

[rmisev]

I think it may be useful to add test written in JS, say with following cases:

• new URL("file:///").origin === new URL("blob:file:///").origin
• new URL("file://host/").origin === new URL("blob:file://host/").origin

[anonrig]

These changes are not sufficient enough for us to verify the correctness. Can you also add a Javascript test as well? Additionally, do we need to change any wording in the specification itself?

[annevk]

@anonrig see the link in OP.

I'm not sure we can create those tests @rmisev. While I think I agree with them in spirit, in theory at least the specification allows for those to not be equal.

[rmisev]

I'm not sure we can create those tests @rmisev. While I think I agree with them in spirit, in theory at least the specification allows for those to not be equal.

Hmm, after whatwg/url#780 the specification says this about the origin of blob URL:

4. If pathURL’s scheme is "http", "https", or "file", then return pathURL’s origin

So for blob:file://host/ it must return the origin of file://host/. In other words:
new URL("blob:file://host/").origin === new URL("file://host/").origin
Why do you say that they can be unequal?

[annevk]

Because

Unfortunate as it is, this is left as an exercise to the reader.

could return a random string, for instance.