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

The file API defines not only the origin of a blob, but also the origin of a blob URL. And defines the origin of that URL to be the same as that of the context that creates it. In particular when that origin is an opaque origin the origin of the blob URL needs to still be the same origin with it. That is impossible to do through serialization and deserialization via the URL itself (separately the FileAPI spec doesn't actually define how implementations should serialize an opaque origin in a blob URL, it leaves that implementation defined). But some out-of-band data (like the already existing Blob URL store) is needed to actually have blob URLs be same origin with the context that created them.

---
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-226415814

Received on Thursday, 16 June 2016 08:04:29 UTC