Re: [w3c/FileAPI] Blob URL store partitioning (#153)

> Apart from the issues discussed above that would not work well for top-level navigations to partitioned blob: URLs.

What are the issues above?  I looked at the links but it was not obvious to me.  Dynamic keying?  Not all browsers are proposing to do that.

And I don't see why its problematic for top-level navigations.  Can you explain that?  If we have a StorageKey for the blob we can propagate that to the context.  Just like how we are going to have partitioned service workers if they are registered with a partitioned StorageKey.

But even if we wanted to prevent blob URLs from partitioned StorageKeys from being navigated to, I don't see why we need to block a context with the same StorageKey as the blob from loading it as a subresource.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/153#issuecomment-868739700