W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2014

Re: [whatwg] ImageBitmap feature requests

From: Justin Novosad <junov@google.com>
Date: Tue, 20 May 2014 16:01:00 -0400
Message-ID: <CABpaAqQE9BVUG00CsmzBwL2JLB+Rhe1a9m9AuL0YN1ReMoFSQA@mail.gmail.com>
To: "Robert O'Callahan" <robert@ocallahan.org>
Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>, Ian Hickson <ian@hixie.ch>
On Sun, May 18, 2014 at 11:02 PM, Robert O'Callahan <robert@ocallahan.org>wrote:

> On Sat, May 17, 2014 at 4:18 AM, Anne van Kesteren <annevk@annevk.nl>wrote:
>
>> Maybe we should have <img>.srcObject similar to what we're doing for
>> media elements. <img>.src can simply return about:imagebitmap or some
>> such. That way you can also assign a Blob to an <img> element without
>> having to do the weird createObjectURL() hack that might leak memory
>> if you're not careful.
>>
>
> I like this approach, but I think it's simpler to continue to have
> HTMLImageElement.src reflect the "src" content attribute.
>
> I wonder what kind of broader effect it would have if image content can no
longer be uniquely identified or retrieved using a URL. In many places in
Blink/WebKit (and presumably other implementations as well) URLs are used
as keys and handles for image resources. All of that would have to be
refactored.
Received on Tuesday, 20 May 2014 20:01:28 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:20 UTC