NEW274420
An AVIF image is displayed blank in WebKit
https://bugs.webkit.org/show_bug.cgi?id=274420
Summary An AVIF image is displayed blank in WebKit
yann
Reported 2024-05-20 14:58:42 PDT
Created attachment 471454 [details] Webkit logo P3 converted to AVIF using Imagemagick When an AVIF image is opened directly into the browser, the colors are not treated the way they should. For instance, photos with a P3 ICC profile will be displayed as SDR, but in a webpage, inside an img tag, the colors will be treated correctly. Sometimes it can get worse. As an example, I attached the webkit logo that was included in a blog post on Webkit.org (https://webkit.org/blog-files/color-gamut/) This is the HDR version converted with Imagick (installed with Brew, version 7.1.1-32 Q16-HDRI). It has been converted without any special option (convert xxxx.png xxxx.avif) If I try to open it by dropping the file into Safari's window, all I get is a blank page (Brave and Firefox display the correct image, same for the Preview app of macOS). Even in an img tag, Safari can't display this file... except if I drag'n'drop it on the special start page of Safari (to use it as a background image).
Attachments
Webkit logo P3 converted to AVIF using Imagemagick (16.17 KB, image/avif)
2024-05-20 14:58 PDT, yann
no flags
Alexey Proskuryakov
Comment 1 2024-05-22 11:05:19 PDT
Thank you for the report. Let's use this bug to track the *second* issue here, as it has a test case. Could you please file a new bug with a test case for the first issue? I can reproduce that the attached image is blank, both in an ImageDocument and inside an <img>, even though ImageIO matches other browser's behavior.
Radar WebKit Bug Importer
Comment 2 2024-05-22 11:05:32 PDT
Said Abou-Hallawa
Comment 3 2024-05-23 12:14:49 PDT
The attached AVIF image is displayed fine in WK1.
yann
Comment 4 2024-05-23 15:32:46 PDT
(In reply to Alexey Proskuryakov from comment #1) > Thank you for the report. Let's use this bug to track the *second* issue > here, as it has a test case. Could you please file a new bug with a test > case for the first issue? The second bug is there: https://bugs.webkit.org/show_bug.cgi?id=274623
Note You need to log in before you can comment on or make changes to this bug.