iOS 14 can't display certain webp files, but webpinfo doesn't mark them as broken

[Andreas Grunewald]

Hello, 

I am not sure if this is the right place to ask this question but we came across an issue with iOS 14 this week where certain webp images would simply not render inside of Safari 14.

We are leveraging the image api from contentstack.io to resize and convert webP images. All the images work in Chrome and all of them show valid with the webpinfo command line tool but something is breaking some of the images.

We created a codepen https://codepen.io/grunewald/full/ExNyvOr that shows this issue. If loaded on an iPhone with iOS 14 any pictures marked "broken" didn't render for us. 

If anyone has any idea or pointers what the problem might be, any pointers are welcome.

Thanks,

Andreas

[James Zern]

Hi Andreas,

On Mon, Feb 8, 2021 at 12:08 PM Andreas Grunewald <agrun...@bestbuycanada.ca> wrote:

Hello, 

I am not sure if this is the right place to ask this question but we came across an issue with iOS 14 this week where certain webp images would simply not render inside of Safari 14.

We are leveraging the image api from contentstack.io to resize and convert webP images. All the images work in Chrome and all of them show valid with the webpinfo command line tool but something is breaking some of the images.

We created a codepen https://codepen.io/grunewald/full/ExNyvOr that shows this issue. If loaded on an iPhone with iOS 14 any pictures marked "broken" didn't render for us. 

Thanks for providing the sample. I've seen this reported elsewhere too and I think it extends to Safari 14 as well as MacOS 11.2 (via Preview.app for example). All of the images I've looked at have been valid webp and as you mention work in Chrome, so I think this comes down to the decoder being used on those platforms (maybe via ImageIO.framework).

Looking quickly I see this bug in WebKit, which seems related:

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

 

If anyone has any idea or pointers what the problem might be, any pointers are welcome.

Thanks,

Andreas

--
You received this message because you are subscribed to the Google Groups "WebP Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webp-discuss...@webmproject.org.
To view this discussion on the web visit https://groups.google.com/a/webmproject.org/d/msgid/webp-discuss/f3e5da8a-e1fa-4ce5-b41f-0e8a149d54dbn%40webmproject.org.

[Andreas]

Thank you so much James,

this definitely helps. So that might break plenty of sites that use automated webp encoding based on accept headers. So does that mean using webp on apple products is still an issue at this point?

-Andreas

[James Zern]

On Mon, Feb 8, 2021 at 5:05 PM Andreas <agrun...@bestbuycanada.ca> wrote:

Thank you so much James,

this definitely helps. So that might break plenty of sites that use automated webp encoding based on accept headers. So does that mean using webp on apple products is still an issue at this point?

It does seem somewhat related to the content, with a workaround mentioned in the webkit bug, but I think the decision to use webp with safari will be up to each application. I verified your sample was failing on Safari 14.0.3 / MacOS 11.2 while I had an update pending for 14.1 / 11.3 beta, that seems to contain a fix.

[Andreas]

I just tried this again with the latest iOS 14.5 beta looks like it might be fixed.

[James Zern]

On Fri, Feb 12, 2021 at 4:32 PM Andreas <agrun...@bestbuycanada.ca> wrote:

I just tried this again with the latest iOS 14.5 beta looks like it might be fixed.

Great, thanks for letting us know.