If the above image is not animated, your browser does not support Animated PNGs. Just wanted to know whose browser can, and cannot.
If the above image is not animated, your browser does not support Animated PNGs. Just wanted to know whose browser can, and cannot.
Last edited by coldReactive; October 14th, 2009 at 12:39 AM. Reason: Warning to Dial-Up
Cool, I see it with Firefox Minefield/3.7a1pre
Damn straight it does.
Firefox 3.5 and latest Opera - works just fine.
works in links 2.2
Firefox 3.0.14, yes ( Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.14) Gecko/2009090216 Ubuntu/9.04 (jaunty) Firefox/3.0.14)
APNG is just a dirty hack by Mozilla anyway. It is not part of the official PNG specs and the official libpng does not support it, so a browser should not be expected to support it.
http://en.wikipedia.org/wiki/Portabl...hics#Animation
Yeah, they'd rather we use the bloated and difficult MNG format instead, which will never happen because all of the major browser manufacturers have considered and rejected it as a possibility.
Unlikely. I read the comments when they were rejecting it.
One said they'd change their vote from NO to ABSTAIN if the APNG format stopped using the PNG MIME-type and extension (i.e. remove all of the advantages APNG has over MNG), and from ABSTAIN to YES if they added support for JNG and similar (i.e. turn APNG into into MNG under a different name). Another said the PNG situation was not like GIF, which was made with animation from the beginning (which is not true, the original GIF87a format had not animation, that was added with GIF89a).
They also said APNG "violates an established web standard" and suggested the even more hideous PNG-in-GIF hack as an alternative. Which I read as "violate an established web standard if you want, just don't violate our established web standard". Damn hypocrites.
They had their chance to be reasonable, and they chose to ignore what everyone else wants and persist in pushing the already-failed MNG format. It's time to ignore them unless, like the W3C already did with HTML 5.0, they finally relent and face reality. But that's no reason to stop current work.
Bookmarks