W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

Re: [FileAPI] createObjectURL isReusable proposal

From: Bronislav Klučka <Bronislav.Klucka@bauglir.com>
Date: Fri, 03 Feb 2012 16:03:16 +0100
Message-ID: <4F2BF734.4050104@bauglir.com>
To: public-webapps@w3.org


On 3.2.2012 15:13, Anne van Kesteren wrote:
> On Thu, 02 Feb 2012 22:40:12 +0100, Ian Hickson <ian@hixie.ch> wrote:
>> On Thu, 2 Feb 2012, Arun Ranganathan wrote:
>>> 2. Could we modify things so that img.src = blob is a reality? Mainly,
>>> if we modify things for the *most common* use case, that could be 
>>> useful
>>> in mitigating some of our fears. Hixie, is this possible?
>>
>> Anything's possible, but I think the pain here would far outweigh the
>> benefits. There would be some really hard questions to answer, too (e.g.
>> what would innerHTML return? If you copied such an image from a
>> contentEditable section and pasted it lower down the same section, would
>> it still have the image?).
>
> My idea was that innerHTML and getAttribute and such would get back 
> about:blob or some such. I think having the same object associated 
> with two images should be fine, so copy & pasting should probably 
> work. about:blob is just for serialization purposes.
>
>

How would you create copies programmaticaly? How would you reassign src 
attribute of one image to another? The idea, that sometimes the 
attribute would return string (regular URL, FileSystem APi URL) 
sometimes Blob...
What would you do in case like this

img.src = blob;
div.appendChild(img);
var s = div.innerHTML;
div.innerHTML = '';
div.innerHTML = s;

which would work with regular URL, would fail in your suggestion...


B.
Received on Friday, 3 February 2012 15:03:50 GMT

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