[Webkit-unassigned] [Bug 185833] Add APNG as a supported MIME type

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri May 25 10:12:49 PDT 2018


Said Abou-Hallawa <sabouhallawa at apple.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #9 from Said Abou-Hallawa <sabouhallawa at apple.com> ---
In WebKit we only support the mime types of the officially approved image file formats. You can find the list of the supported mime types in initializeSupportedImageMIMETypes() and the corresponding list of the supported UTIs in allowedImageUTIs() .

A file format extension does not require a new UTI or a new MIME type. For example the animated GIF is an extension to the GIF file format. It does have the same extension, the same UTI and the same mime type as the static GIF image.

According to https://en.wikipedia.org/wiki/APNG: "The PNG group officially rejected APNG as an official extension on April 20, 2007." But like other browsers do, WebKit considers the APNG an extension to the PNG file format.

WebKit is capable of displaying and animating an <img> or <picture> with an APNG source as long as you provide "image/png" as its mime type or do not provide it at all. For example, your test case will work without any source change if you change 

    type="image/apng" => type="image/png"

It will work also if you delete the type attribute. The mime type will be deduced from the file extension.

So I do not see any benefit from fixing this bug.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180525/fa1c1919/attachment.html>

More information about the webkit-unassigned mailing list