On Mon, Jul 12, 2010 at 9:59 AM, David Levin <le...@google.com> wrote:
> > > On Mon, Jul 12, 2010 at 9:54 AM, Adrian Bateman <adria...@microsoft.com>wrote: > >> On Monday, July 12, 2010 9:32 AM, David Levin wrote: >> > On Mon, Jul 12, 2010 at 8:39 AM, Adrian Bateman <adria...@microsoft.com >> > >> > wrote: >> > The behaviour would have to be explicitly specified and not left to >> depend on >> > indeterminate browser implementations. >> > >> > Yes. Unfortunately, another way of saying that "the url lives as long as >> the >> > Blob lives" is "the url lives until the Blob is garbage collected". This >> > exposes a very indeterminate behavior. >> >> Exactly. So what I'm saying is the spec needs to say more than just that. >> It needs to make further guarantees. >> >> > >> http://lists.w3.org/Archives/Public/public-device-apis/2010Jul/0000.html >> > See point #5 basically once a load has started for a url, that >> > load should succeed and revoke may be called. >> >> I read point #5 to be only about surviving the start of a navigation. As a >> web developer, how can I tell when a load has started for an <img>? Isn't >> this similarly indeterminate. >> > > As soon as img.src is set. > > > "the spec could mention that the resource pointed by blob URL should be > loaded successfully as long as the blob URL is valid at the time when the > resource is starting to load." > > > Should apply to xhr (after send is called), img, and navigation. > > > Right, it seems reasonable to say that ownership of the resource referenced by a Blob can be shared by a XHR, Image, or navigation once it is told to start loading the resource. -Darin > >> Regards, >> >> Adrian. >> > >