Regarding; input type=image src=a.gif /
Using Firebug's (FF 2) net monitoring, I noticed that every time I
switched the src of an input image it would request the new src image
from HTTP. FF simply does not cache these images. This is kind of
annoying because it can waste a lot of bandwith or
Brice Burgess schreef:
Regarding; input type=image src=a.gif /
Using Firebug's (FF 2) net monitoring, I noticed that every time I
switched the src of an input image it would request the new src image
from HTTP. FF simply does not cache these images. This is kind of
annoying because it
Are you sure about the multiple reload requests? I just checked it out
(via the w3schools) and it isn't happening with Firefox 1.5.
JavaScript:
var imgnum = 0;
var imgs = ['paper.jpg','bgdesert.jpg'];
function srcCh(e)
{
e.src = imgs[imgnum];
imgnum = imgnum ? 0 : 1;
}
HTML:
Klaus Hartl wrote:
Brice,
I think having two images in the HTML source is pretty ugly. I once did
an Image image Replacement for inputs with type image. That way you
can easily use pure CSS hovers and use CSS sprites to avoid traffic. It
also makes skining much easier, as the appearance
Karl Rudd schrieb:
Are you sure about the multiple reload requests? I just checked it out
(via the w3schools) and it isn't happening with Firefox 1.5.
Maybe the cache was disabled, which I always do of course when developing.
-- Klaus
___
jQuery
On 16/02/07, Brice Burgess [EMAIL PROTECTED] wrote:
Klaus Hartl wrote:
Brice,
I think having two images in the HTML source is pretty ugly. I once did
an Image image Replacement for inputs with type image. That way you
can easily use pure CSS hovers and use CSS sprites to avoid traffic.
Brice Burgess schrieb:
Klaus Hartl wrote:
Brice,
I think having two images in the HTML source is pretty ugly. I once did
an Image image Replacement for inputs with type image. That way you
can easily use pure CSS hovers and use CSS sprites to avoid traffic. It
also makes skining much
