25746 - Problem with cursors.com content

Status: VERIFIED FIXED

(Core :: DOM: Core & HTML, defect, P3)

Description

[Adam]

Mozilla  has a problem executing the Javascript code on this site. The script is for animating the 'sprockets' images on the homepage. The 
sprockets rotate in an inconsistent and very rigid manner. Testing on Communicator 4.7 shows that they should rotate in a fluid and repetitive 
manner.  The javascript code is below:

<script language="JavaScript">

<!--
        if(document.images) {
                ftover = new Array(2);
                ftout = new Array(2);
                for(var n=1;n<=4;n++) {
                        ftover[n]=new Image(57,57);
                        ftout[n]=new Image(57,57);
                        ftover[n].src="red_yel.gif";
                        ftout[n].src="red_yel_static.gif";
                }
        }
        function tabOn(i) {
                if(document.images) document.images["ft" + i].src=ftover[i].src;
        }
        function tabOff(i) {
                if(document.images) document.images["ft" + i].src=
ftout[i].src;
        }
//-->

</script>

Mozilla fails to correctly execute this script - the images should rotate in a consistent manner but in Moz they're too 'herky-jerky' (<--scientific!) 
and very inconsitent.

I experienced this running Mozilla-Mac-M14 (200001908) with Mac OS 9.

Comment 1

[vidur (gone)]

Well, the sprocket animation is just done through an animaged GIF. The 
performance issues are in our animated GIF/gfx/compositor code. Passing this one 
along to Pam Nunn to see if there are known animated GIF problems.

Comment 2

[pnunn]

I'll check it out.
-p

Comment 3

[Adam]

I checked out www.cursors.com tonight w/ MozMacM14 (2000022108) OS 9 and the
GIFs seem to be working fine - pretty much perfect as far as speed/display etc.
goes. Has a fix been checked in for this or is this the result of some other
fixes? Possibly fixed; might need 'verifyme' keyword.

Comment 4

[pnunn]

Several fixes for other bugs have been checked
in and may have fixed this bug.

If you are happy, I am happy. (and going on to other bugs.)

I'm closing this one. 
Thanks for your quick feedback.
-P

Comment 5

[Adam]

No problem. Going to add 'verifyme' keyword to get it closed for good.

Comment 6

[Prashant Desale]

Verified with 02-29-09