[Webkit-unassigned] [Bug 245097] WebKit is incorrectly selecting a picture source it does not support

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Sep 15 14:21:56 PDT 2022


https://bugs.webkit.org/show_bug.cgi?id=245097

--- Comment #13 from Sam Sneddon [:gsnedders] <gsnedders at apple.com> ---
(In reply to Said Abou-Hallawa from comment #9)
> If you open
> https://cdn.xeiaso.net/file/christine-static/talks/my-website/001.avif in
> Preview and you show the inspector for the Tools menu, you will see that the
> format of this is image is HEIF image.
> 
> When calling the function CGImageSourceGetType() for this image, we get
> "public.heif". Since we are not supporting HEIF right now, WebKit fails to
> render this image.

But we do support HEIF now, hence why we can render any AVIF image (which is, after all, AV1 in HEIF).

> I think the reason for returning "public.heif" is this image is a HEIF
> container which contains an AVIF image. So it is hard to argue
> CGImageSourceGetType() returns the wrong UTI.
> 
> The fix is either to make CGImageSourceGetType() return "public.avif" for
> this image or to enable HEIF/HEIC in WebKit.

This would just make WebKit wrong for other HEIF images, no? We currently support AVIF (AV1 in HEIF), bug 244424 is about adding support for HEIC (HEVC in HEIF), but it's at least also defined how to package JPEG, AVC, JPEG2000, and others in HEIF, plus likely other future types within the HEIF container.

Is your proposal that WebKit should allow any possible contents within an HEIF container, and we should add support for all defined payloads of the container format?

-- 
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/20220915/cac744d3/attachment.htm>


More information about the webkit-unassigned mailing list