[Webkit-unassigned] [Bug 26455] GIF clamping time differs from Firefox

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=26455





------- Comment #1 from mjs at apple.com  2009-06-16 14:43 PDT -------
Normally we follow Firefox instead of IE for otherwise arbitrary Web
compatibility issues, unless we think following IE will give better
compatibility. Part of the reason we do that is due to the prevalence of dual
code path sites. In this case though, it's unlikely a site will have different
versions of an animated GIF for Firefox and IE. Some thoughts:

1) It seems that, for reasons stated above, following IE is probably the right
default choice for this issue, in the absence of other reasons.

2) Making the clamp limit lower does seem more right in the abstract - the main
purpose of having a limit is to give reasonable behavior for a frame time of 0
or other unreasonably low values. But an animated GIF should be allowed to
legitimately do 60fps.

3) The exact details of the clamping limit don't seem hugely important. For
high quality animations it's likely better to use a real video codec, and
current animated GIF uses seem to be in situations where quality of
presentation is not a prime concern.

Given this, I'm personally fairly indifferent between the options.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.