The Windows GDI+ library cannot tell when a GIF frame does not have a delay specified. It returns a BYTE array for frame delays with values starting at zero. The GIF98a standard actually says that if a delay is not specified, the GIF should be animated without delay, ie. a zero delay. The treating of "no delay specified" as different delay values by different browsers, applications, websites, etc. is just down to the developer of the application, eg. every browser uses a different value for "no delay specified" or even delays that are too small. I believe it was originally a way of handling broken GIFs by inserting minimum delays between frames to avoid excess CPU usage. Basically, if a frame has no delay specified, it is correct to assume that the delay should be zero.
Aaand... I think we are done with this particular discussion. I am now off to have a nice morning walk in the park with my dog :-) Enjoy your weekend everyone.
