Re: [w3c/FileAPI] Partition Blob URL revocation by Storage Key (PR #201)

@mkruisselbrink commented on this pull request.

looks good to me as well, modulo Anne's nits

> @@ -1595,6 +1609,22 @@ as the serialization of the origin of the environment that created the blob URL,
 but for opaque origins the origin itself might be distinct. This difference isn't
 observable though, since a revoked blob URL can't be resolved/fetched anymore anyway.
 
+### Access restrictions on blob URLs ### {#partitioningOfBlobUrls}
+
+<a>Blob URLs</a> can only be fetched from environments where the [=storage key=] matches that of
+the environment where the <a>blob URL</a> was created. <a>blob URL</a> navigations are not subject

```suggestion
the environment where the <a>blob URL</a> was created. <a>Blob URL</a> navigations are not subject
```

(capitalize start of sentence)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/pull/201#pullrequestreview-2476794000
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/FileAPI/pull/201/review/2476794000@github.com>