User-Agent: Mozilla/4.8 [en] (WinNT; U) Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4a) Gecko/20030401 The GIF89a allows to set a frame rate, i.e., 20 millisecond (50 frames/second). The IE 5.# was/is unable to handle movi like GIFs and has therefor set a lower frame rate of 100 milliseconds by violating the GIF89a standard! (For more frames then about 100/second are not practical a lower limit may be set to 10 milliseconds, not 100, which hinderes movie like GIFs. All Netscape Browsers up to version 4.x and also Opera (i.e. 7.#) do it in the right way. I wish, the programmers of Mozilla should not follow the bad and standard violating programming scills of Microsoft!! Please, repair this! Reproducible: Always Steps to Reproduce: 1. load: http://www.rschr.de/Bilder/Doppelst.gif 2. http://www.rschr.de/Bilder/Dcep.gif Actual Results: The GIF89a (Doppelst.gif) contains 256 frames, 20 milliseconds each, resulting in about 5 seconds for one complete revolution. It's impossible to create smooth movement due to 100 milliseconds/frame set by Mozilla, as you can see! The Dcep.gif is even worse: 124 frames, 20 milliseconds each, should result in a period of about 2.5 seconds th demonstrate the smooth collor changing of this star. Impossible now! Expected Results: I hope, that the imtroduced bug (by report #125137) will be repaired, either by setting the lower frame limit to 10 milliseconds or by introducing the feature to set somewere under "Preferences", "Advanced" "GIF89a speed limit" or "IE like". Be proud of your product, but don't follow Microsoft's buggy programmed and standard violating IE!!

Yeah, but there are also many webpages which depend on that (we got enough 'animations are going too fast' bugs).

*** This bug has been marked as a duplicate of 71829 ***

Mozilla schould keep standards, NOT help Microsoft to destroy them! GIF89a is still widely used and by far the easiest way to include amimated images. A lot of GIFs require to be run with frame rates highter then 10 per second. It's a bad idea to somehow follow the bugs IE contains! OPERA is keeping the GIS89a standard! To support bad programmed GIFs, you could allow the user to set the lower limit for the delay.

This should be a dupe of bug 139677, but it seems that it will be a Mac-only fix. You can alwasy ask to fix it for other platforms too. It's unfortunate that Exploder limits the frame rate to 100ms (only on Windows, the Mac version is ok), but they can't correct their own mistake either. Too many users would complain that their animations are suddenly going to fast, wihtout realizing that the fault is in image itself. And that's what bug 71829 is about. Mozilla had to follow IE, we had no choice. Bug 139677 wants to fix that for the Mac only, becuase Mac IE doesn't have that limit. IMHO, when you have an animation that goes really fast, you shouldn't be surprised that it will be slower or 'stutter' in some situations. Not very computer is fast enough, some webbrowsers have a very slow display (X over a network for instance), there might be other objects on that page that require a lot of cpu (Flash, Java), ... HTML is not an animation platform !

Jo Hermans wrote: > ... Mozilla had to follow IE, we had no choice. Hi Jo, I don't understand this argument. Why had Mozilla to follow the IE, in particular concerning wrong handling of GIF89a images? Is there then any reason NOT to use IE? > IMHO, when you have an animation that goes really fast, you > shouldn't be surprised that it will be slower or 'stutter' in some > situations. Not very computer is fast enough, some webbrowsers have > a very slow display (X over a network for instance), there might be > other objects on that page that require a lot of cpu (Flash, Java), > ... HTML is not an animation platform ! excuse me, but HTML is (also) an animation platform (IMHO)! Speed is no more an argument: today computers are easily capable of handling animations like GIF89a images. I'm still using an AMD K6-2 400MHz CPU, the CPU usage for the example: http://www.rschr.de/Bilder/Dcep.gif under Netscape 4.8 or Opera 7.1 is almost not even measurable! But I agree: Flash and Java do need much more CPU power. Mozilla has a lot of excellent features better then IE, i.e. correct handling of UTF-8 code, but the 'mishandling' of GIF89a images is really annoying! If this bug is corrected for the Mac OS, then it should also be corrected for Windows and for Linux. The more I became aware of the fact that the Mozilla developers try to follow bugs of IE, the more there is no need to use Mozilla instead. At least this is true for me. Have a nice day, Rolf

I realize this is a hot issue, but it's also definitely a dupe of bug 125137. There's nothing "false" about 125137. Please take any comments over there so this discussion can be kept in one place rather than fragment across multiple bugs, unless someone feels this is *definitely* a different issue than the multiple other bugs relating to animated gif speed are about. Thank you. *** This bug has been marked as a duplicate of 125137 ***

Jo Hermans wrote: > ... Mozilla had to follow IE, we had no choice. Just thought that I would point out that Mozilla chose to follow _Windows_ IE. The Mac version of IE does not have the limitation. In fact Mozilla is the ONLY Mac browser to forces a 100ms minimum delay. Also, it is absurd to say that Mozilla had no choice. The appropriate choice would have been to evangelize the fact that some ignorant web designers were not setting the proper delay in their GIFs. Instead Mozilla volunteered to start displaying many animated GIFs incorrectly. Mozilla had a choice; unfortunately the powers that be arbitrarily decided that it was somehow better to show properly designed GIFs too slow rather than show improperly designed GIFs too fast; thus now Mozilla is one of the few browsers to not follow the standard.