Comment #22 on issue 295 by rablaridash: Animated GIF issues http://code.google.com/p/chromium/issues/detail?id=295
I get the impression that there are deeper issues at work here. However, it is not true that "On the web, correct behavior _is_ to be consistent with other browsers." Correct behavior is compliance to standards, such as the HTML or CSS specs. Doing things simply because IE does them is not correct behavior. I've seen plenty of issues here that are marked Evangelism because Chrome is doing the right thing - in contradiction to the behavior of other browsers - and the response is essentially that the web designer should be encouraged to correct their code instead of depending on incorrect behavior. Look at Issue 7237, for example. In regards to this specific issue, why do browsers have timing clamps at all? Why not display the animation at the rate its creator intended and encoded into the file? What your suggesting is that it is correct behavior to animate an animated image at an arbitrary clamped rate instead of the rate in the file. That doesn't make any sense. So while I supposed this could be "working as intended", it's certainly not "correct behavior". Animated files are not being displayed correctly. They're being displayed as other browsers have displayed them in the past, but not the same as any other software capable of displaying them (Easy ubiquitous-on-Windows example: Windows Picture and Fax Viewer). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
