- From: Glenn Maynard <glenn@zewt.org>
- Date: Sat, 4 Feb 2012 08:19:27 -0600
- To: Bronislav Klučka <Bronislav.Klucka@bauglir.com>
- Cc: public-webapps@w3.org
- Message-ID: <CABirCh_9wJfpdye75Rte7asy2i9K=s7fDqkSf_iQPRtE9xu3DQ@mail.gmail.com>
If you can't be civil, I'm not going to discuss with you. 2012/2/4 Bronislav Klučka <Bronislav.Klucka@bauglir.com> > > > On 4.2.2012 5:55, Glenn Maynard wrote: > >> 2012/2/3 Bronislav Klučka <Bronislav.Klucka@bauglir.com <mailto: >> Bronislav.Klucka@**bauglir.com <Bronislav.Klucka@bauglir.com>>> >> >> >> 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... >> >> >> This would fail just as badly with auto-releasing URLs. No approach so >> far makes this work (other than the explicit releasing that we're trying to >> give alternatives to). >> >> -- >> Glenn Maynard >> > > It's like talking to a wall sometimes > DO NOT USE AUTO RELEASING URL IF YOU ARE GOING TO REUSE IMAGE > :) > > I my approacha using cache-like blob URL did solve that :) > > Brona > -- Glenn Maynard
Received on Saturday, 4 February 2012 14:19:55 UTC