The only places using gdk-pixbuf in Firefox for loading images are all for loading images from your local machine. No from-the-network code paths use gdk-pixbuf.
You'll note that APNG does support variable frame rates and location of images at positions other than (0,0). Neither of these are complex features and the latter allows you to have smaller subsequent frames ala GIF resulting in much smaller animations.
We are changing the format of APNG so that all the frames live inside of a single IHDR/END. This should resolve any problems you might have. v0.3 of the spec (should be out tomorrow) will have these changes.
APNG files _are_ PNG files. We didn't create a whole new format (since that would be silly) so APNG files will still be.PNG files. The first frame in an APNG file looks to current PNG decoders to just be a regular PNG. The APNG spec specifies some additional chunks that if found tell an APNG aware decoder how to find the rest of the frames.
The standard way to animated JPEGs in the past has always been using server push (multipart/x-mixed-replace). Mozilla does support this. A lot of webcam sites use this.
Think about uses of animations in applications. The Mozilla UI guys would love to be able to do a nice looking (no sharp edges, nice transparency, etc) throbber images.
We were only aiming to replace animated GIFs. MNG does have some interesting properties which may make it more useful for things like this, however it has been my experiance talking to web developers that the thing they really want is a small fast easy to use animated GIF replacement.
We only use a single code path for rendering images. We only use gdk-pixbuf to decode GNOME images to find icons for mimetypes.
Mozilla does not use gdk-pixbuf for drawing images -- stuart "pavlov" parmenter (mozilla image library owner)
The only places using gdk-pixbuf in Firefox for loading images are all for loading images from your local machine. No from-the-network code paths use gdk-pixbuf.
You'll note that APNG does support variable frame rates and location of images at positions other than (0,0). Neither of these are complex features and the latter allows you to have smaller subsequent frames ala GIF resulting in much smaller animations.
We are changing the format of APNG so that all the frames live inside of a single IHDR/END. This should resolve any problems you might have. v0.3 of the spec (should be out tomorrow) will have these changes.
We're actually changing the format to have everything inside a single IHDR/IEND. This won't be a problem in v0.3 of the spec.
There are no additional PNG headers for the additional IHDR/IENDs, so you should have no trouble finding the next image by looking for a PNG header
It doesn't. It wouldn't be super hard to add, but no one has ever asked for it, so I never added it to imagelib.
It wouldn't suprise me to see at least the minority browser vendors supporting APNG in the not so distant future...
Vlad and I are currently looking at adding composite operators as well as disposal methods such as those in GIF. They should be in the spec by 1.0.
APNG files _are_ PNG files. We didn't create a whole new format (since that would be silly) so APNG files will still be .PNG files. The first frame in an APNG file looks to current PNG decoders to just be a regular PNG. The APNG spec specifies some additional chunks that if found tell an APNG aware decoder how to find the rest of the frames.
The standard way to animated JPEGs in the past has always been using server push (multipart/x-mixed-replace). Mozilla does support this. A lot of webcam sites use this.
Think about uses of animations in applications. The Mozilla UI guys would love to be able to do a nice looking (no sharp edges, nice transparency, etc) throbber images.
JNG won't be part of APNG. JNG is really its own spec and shouldn't really be related to MNG except that libmng can decode JNGs.
We were only aiming to replace animated GIFs. MNG does have some interesting properties which may make it more useful for things like this, however it has been my experiance talking to web developers that the thing they really want is a small fast easy to use animated GIF replacement.