UNCONFIRMED 27659
IMGs don't animate in Safari
https://bugs.webkit.org/show_bug.cgi?id=27659
Summary IMGs don't animate in Safari
Aditya Mukherjee
Reported 2009-07-24 11:42:53 PDT
As demonstrated in the attached file, the images are meant to "grow" as and when they're loaded. This works as expected in Firefox and Chrome, but not in Safari 4. The commented out line, however, works in all three browsers as expected. It's the same case when the images are made to "fade" in (doesn't work in Safari, works in Firefox and Chrome), if that helps.
Attachments
Testcase for bug. (1.53 KB, text/html)
2009-07-24 11:43 PDT, Aditya Mukherjee
no flags
Aditya Mukherjee
Comment 1 2009-07-24 11:43:34 PDT
Created attachment 33456 [details] Testcase for bug.
Aditya Mukherjee
Comment 2 2009-07-24 11:47:09 PDT
Okay, correction: the bug is not consistent. I'll try to come up with a more consistent test case if I can, while someone reviews this.
Simon Fraser (smfr)
Comment 3 2009-08-02 15:18:56 PDT
How are you animating the images? The testcase is not simple enough.
Aditya Mukherjee
Comment 4 2009-08-05 22:50:20 PDT
They're being animated by Javascript (jQuery's "animate()" function). I believe it's a simple change of width and height from 0 to the final value with "setIntervals". [I hope that's the answer you were looking for?]
Frances Cornwall
Comment 5 2024-05-02 12:47:53 PDT
The test case appears as blank in Safari 17.4.1.
Said Abou-Hallawa
Comment 6 2024-05-02 13:22:06 PDT
The test case appears as blank in all browsers. I see these messages in the Safari's console window: [Warning] [blocked] The page at https://bug-27659-attachments.webkit.org/attachment.cgi?id=33456 was not allowed to run insecure content from http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js. [Warning] [blocked] The page at https://bug-27659-attachments.webkit.org/attachment.cgi?id=33456 was not allowed to run insecure content from http://api.flickr.com/services/feeds/photos_public.gne?format=json. Similar messages appear also in Chrome and FireFox.
Note You need to log in before you can comment on or make changes to this bug.