-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AVIF images are broken in Chrome Canary #91
Comments
Awesome, thank you! |
Also reported via Twitter https://twitter.com/freshyill/status/1390419540610363393 Progress was made today lovell/sharp#2666 |
Per lovell/sharp#2666 (comment) this has been downgraded from a break-the-web emergency with a fix applied to Chrome Canary 😅 |
Seen in Chrome Dev. |
@jaredgorski where at? |
@zachleat I migrated part of my personal site to use According to my cursory research into these issues on Chrome Canary, the behavior I'm seeing on Chrome Dev matches. Figured I'd mention it here in case this comes as a surprise. |
@jaredgorski Yeah, I appreciate it. I’m eyeing this very closely. There are a bunch of broken images currently in Canary on the https://www.11ty.dev/ home page. I believe these were generated with an old version of Can you try to regenerate your images with the newest versions? |
@zachleat Very interesting; the avatars are all broken in Chrome Dev I'm using I'm unsure of the exact relationship between Canary and Dev in terms of releases, but I wouldn't be surprised if Dev gets Canary code. It seems as if Dev is one step closer to Stable than Canary, since it's a weekly update rather than nightly. |
I can confirm this issue also exists on the Beta version as of Chrome 93. https://github.com/strukturag/libheif/releases/tag/v1.12.0 has the fixed applied. |
I'm using Firefox Nightly, the newly generated avif is also broken. |
Shipped with |
Shipping with |
Per actions failure https://github.com/11ty/eleventy-img/actions/runs/1143536646 this also needs #100. |
AVIF files generated by eleventy-img are not working in recent Chrome Canary.
The underlying issue is with libheif, used by sharp, used by eleventy-img.
I've raised related issues with Chromium and with sharp recently.
Opening one here as well so that maintainers are aware of the issue and will know to update sharp dependency as soon as the fixed version is released.
The text was updated successfully, but these errors were encountered: