On 09.05.2014 23:29, Arun Ranganathan wrote: > .. > So this is problematic: we don’t have a common syntax on the web, and > even implementations which share code don’t do it exactly the same. Of > course, blob: URLs aren’t supposed to be human readable, or really > viewed by the developer. But not having a good way to denote origin > within the URL that signifies the origin of the incumbent settings > object is problematic for Fetch and Parse specifications that need > origin information.
Wouldn't it be nice if there was a programmatic way to probe if a blob URI belongs to a specified origin or not? If they had an origin attribute one could compare them to location.origin or so. But well, they are DOMStrings and not objects...
