Fading img's / input type="image"'s

[zelnugget]

I'm using a fading image script that I found via Google Groups on this
newsgroup, and am having some difficulty with it. First, here's a link
to the Google Groups posting:

http://groups-beta.google.com/group/...287a2f20de1b10

I've modified the page linked to in the above URL by making one of the
images an input element whose type is an image and am now encountering
flickering problems. Here's the webpage:

http://geocities.com/zelnugget/fade.html

Any ideas as to what I could do to fix this problem?

Also, I apologize for the page not being HTML4.01 compliant. That's
geocities fault - not mine. If you look at the source code, it should
be easy enough to see how to make the page HTML4.01 compliant (just
remove the code above and after the "remove this code" comments).

[RobG]

zelnugget wrote:
[...]

I've modified the page linked to in the above URL by making one of the
images an input element whose type is an image and am now encountering
flickering problems. Here's the webpage:

[...]

Sorry but the pages are such a mess I couldn't get a good look
at the code. Much better if you put your issue into a simple
script and post the actual code or a suitable snippet.

Have a read of this thread:
<URL:http://groups-beta.google.com/group/comp.lang.javascript/browse_frm/thread/bfc549e41ee70963/a21522fdbe7c893b?q=firefox+bug+flicker&_done=%2Fgr oup%2Fcomp.lang.javascript%2Fsearch%3Fgroup%3Dcomp .lang.javascript%26q%3Dfirefox+bug+flicker%26qt_g% 3D1%26searchnow%3DSearch+this+group%26&_doneTitle= Back+to+Search&&d#a21522fdbe7c893b>

Or if that is too broken by Google Groups, search this news
group for "onMouseOver/onMouseOut not working" about 12 Feb 05.

The flicker is caused by bubbling of events. If you move your
mouse quickly in Firefox, the onmouseout does not always restore
the initial image. This is a bug in Firefox/Mozilla - the
onmouseout does not always fire.

RobB proposed a solution based on CSS and background image that
seems to fix the flicker & onmouseout pretty well, but it is
more a work around and is not actually a cure - some users will
still have an issue with it but far fewer than with your current
code.

--
Rob