Re: [whatwg/url] Origin of blob URLs doesn't match what implementations do (#127)

> I think the standard has a better approach

Which standard. Currently the file API spec and the URL spec disagree here. According to the url spec the origin of a blob url with an opaque origin is a new unique opaque origin, since its created from the serialized url. While according to the file API spec the origin should be the same opaque origin as that of the incumbent settings object that created the URL.

Of course both would serialize to "null", so from the javascript URL API point of view this wouldn't matter, but when other parts of the spec try to determine if URLs are same origin this does matter. In particular for things like creating workers from blob URLs. But also other situations. Should a blob URL be same origin with the setting object that created them or not? I think yes, and I believe implementations agree (at least chrome does). The File API spec certainly agrees. The current URL spec seems to be the odd one out.

---
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/127#issuecomment-226404004