
But there was one time when I made an animation and somebody kept urging me to make it faster, and there was a difference between 0.04 (which I thought at the time was as fast as anything needed to go) and 0.01 (which I didn't think would make a difference, but it did). Granted, nobody would have been seeing every frame at that speed, but firefox played it back faster alright. Edit: maybe 0.02 not 0.01
( ,
Fri 26 Aug 2005, 22:14,
archived)

Unless you use the PRECISE value required to match the maximum fps of FF or IE, then some frames get kind of forgotten. The updates are always done at the rate FF plays back at, so if the frame delay is slightly larger than that, the excess builds up and every few frames, one frame will get played twice. It's a bit shit that way
( ,
Fri 26 Aug 2005, 22:18,
archived)

See above for 0.04 version to compare.

Sorry, what?
You mean the delay between frames is coerced into multiples of the browser's highest frame rate?
( ,
Fri 26 Aug 2005, 22:19,
archived)

Sorry, what?
You mean the delay between frames is coerced into multiples of the browser's highest frame rate?

that won't make me look like a pervert
( ,
Fri 26 Aug 2005, 22:26,
archived)

and the second seems faster. Everyone will tell you that IE is slow and uses 15fps. I thought FF was 25, but it might be higher. Not much higher though.
As I said, the timing of gif playback is shit - it's not precisely what you set the delays too. It tends to choose a "near enough" delay and the rest of the time for that frame spills over to the next. No delay is the best bet for smooth animations, but you have no control over the actual speed between browsers that way.
( ,
Fri 26 Aug 2005, 22:24,
archived)
As I said, the timing of gif playback is shit - it's not precisely what you set the delays too. It tends to choose a "near enough" delay and the rest of the time for that frame spills over to the next. No delay is the best bet for smooth animations, but you have no control over the actual speed between browsers that way.