W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2013

Re: [whatwg] ProgressEvents for Images

From: Glenn Maynard <glenn@zewt.org>
Date: Sat, 5 Jan 2013 20:41:06 -0600
Message-ID: <CABirCh8tvD07RW_Xdj0LqwRGBPnVPgNaJ0e54MhhUzE=aYULig@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: whatwg@whatwg.org
On Thu, Jan 3, 2013 at 9:57 PM, Ian Hickson <ian@hixie.ch> wrote:

>  > The particular case above should be fixed, at least in the most common
> > cases, by auto-revoking blobs, since you'll no longer need to carefully
> > call revokeObjectURL.  (I've come to the conclusion that
> > URL.revokeObjectURL was a very badly flawed idea, since it introduces
> > manual resource management in a platform not designed for it.)
>
> I'm not exactly clear on what exact words are needed here. If you could
> file a bug cc'ing the relevant people with a description of how to make
> this work, that'd be great. (I don't think this should be special-cased
> for <img>; there are dozens of other places in the spec where a URL may or
> may not be fetched for various reasons.)
>

I don't think any changes are needed here, aside from the autoRevoke
feature moving forward.


On Sat, Jan 5, 2013 at 8:06 PM, Garrett Smith <dhtmlkitchen@gmail.com>wrote:

> MSDN mentions a 'onetimeonly' property, and there was an 'isReusable'
> property proposal on some list before.
>
> Having recently had to patch a hot mess of code using that, I agree. It is
> ugly.
>

The IE "onetimeonly" feature has very serious issues, but it was an
important step towards the autoRevoke idea.

-- 
Glenn Maynard
Received on Sunday, 6 January 2013 02:41:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:12 GMT