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

As mentioned in [Origin of Blob URLs](https://w3c.github.io/FileAPI/#originOfBlobURL), the origin of a blob URL should be the origin of the incumbent settings object when the URL was created. The simple "parse the origin from the url in the first string of the path of the blob url" algorithm the URL spec uses doesn't accomplish that for opaque origins.

The way at least chrome implements this is by maintaining a separate blob url -> origin mapping, and using that to lookup the origin of a blob url. I assume firefox does someting similar (see also whatwg/html#1322 for an example where this behavior matters).

Should the URL spec be updated to actually match the File API spec about blob URLs, and to match what implementations seem to do?

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