W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

Re: Lifetime of Blob URL

From: David Levin <levin@google.com>
Date: Mon, 12 Jul 2010 09:59:37 -0700
Message-ID: <AANLkTim6ZZTDTgByKXFp5wOwHqqs-PyjNEsiL6EbByXa@mail.gmail.com>
To: Adrian Bateman <adrianba@microsoft.com>
Cc: "arun@mozilla.com" <arun@mozilla.com>, Web Applications Working Group WG <public-webapps@w3.org>
On Mon, Jul 12, 2010 at 9:54 AM, Adrian Bateman <adrianba@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 <adrianba@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.



> Regards,
>
> Adrian.
>
Received on Monday, 12 July 2010 17:00:07 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:39 GMT