Hmm.. So I put that random number to get beyond the cache. But I only did that for testing purposes so you can try it over and over again to make sure that the image fades in only after it loads. In a live product I wouldn't use that for this scenario. Static images should generally always be cache-able.
Why do you want to prevent caching? On Mar 16, 1:05 am, stratboy <[email protected]> wrote: > :) Interesting. Thank you! > > On 15 Mar, 20:41, jemajoign <[email protected]> wrote: > > > Sometimes I use an approach like this when I am waiting on two > > things:http://jsfiddle.net/bMRth/ > > > Seems to work for me. Does it work on your browser? > > > On Mar 15, 8:08 am, stratboy <[email protected]> wrote: > > > > Hi! Another question. > > > >http://reghellin.unbit.it/test2/ > > > > ONLY in firefox, the fadein fx on the bg that you can see in safari > > > and ie, isn't visible. > > > In fact, it happens, but it happens too early, when the image is still > > > being showed gradually from top to bottom. So it seems that the onload > > > event of Assets doesn't take in account this fact. > > > > BUT in a site like this: > > > >http://ines-papert.de/en/home > > > > they were able to do it even in firefox, apparently simply with this > > > code: > > > > $(function () { > > > var img = new Image(); > > > $(img).load(function () { > > > $(this).css('display', 'none'); > > > $(this).hide(); > > > $('#loader').append(this); > > > $(this).fadeIn(); > > > }).error(function () { > > > }).attr('src', 'http://ines-papert.de/images/116.jpg'); > > > }); > > > > (jquery stuff) > > > > I guess that THAT load event, fires when the image is completely > > > (virtually) visible. > > > > How can I do this with mootools?
