Bug 241512 - REGRESSION (iOS 15.5 ): Sites with images that have loading="lazy" and background-image fail to load
Summary: REGRESSION (iOS 15.5 ): Sites with images that have loading="lazy" and backgr...
Status: RESOLVED DUPLICATE of bug 241435
Alias: None
Product: WebKit
Classification: Unclassified
Component: Images (show other bugs)
Version: Safari 15
Hardware: iPhone / iPad iOS 15
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-06-10 06:22 PDT by dylan
Modified: 2022-06-14 09:43 PDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dylan 2022-06-10 06:22:42 PDT
On iOS 15.5, sites that are loaded in Safari with images that have loading="lazy" and a background-image CSS property will cause the entire page not to load. Safari gives the "A problem repeatedly occurred" error message.
On <15.5, the pages load.

This will NOT load:
https://safari-15-5-background-im-0482ae5a53a72.webflow.io/

These WILL load:
https://safari-15-5-background-im-0482ae5a53a72.webflow.io/without-lazy
https://safari-15-5-background-im-0482ae5a53a72.webflow.io/without-bg-image
Comment 1 Alexey Proskuryakov 2022-06-13 22:25:57 PDT
Thank you for the report!

Can you please let us know whether this affects any live websites?
Comment 2 Radar WebKit Bug Importer 2022-06-13 22:26:06 PDT
<rdar://problem/95083527>
Comment 3 dylan 2022-06-14 06:04:05 PDT
(In reply to Alexey Proskuryakov from comment #1)
> Thank you for the report!
> 
> Can you please let us know whether this affects any live websites?

Yes it does - I'm not sure if I can share any sites directly here, but we learned about this through live sites. I can most likely have them shared privately if needbe, but the 3 provided are the minimal repros based on customer sites. Thanks!
Comment 4 Antoine Quint 2022-06-14 08:15:07 PDT
This got fixed in r295393.

*** This bug has been marked as a duplicate of bug 241435 ***
Comment 5 dylan 2022-06-14 09:43:57 PDT
(In reply to Antoine Quint from comment #4)
> This got fixed in r295393.
> 
> *** This bug has been marked as a duplicate of bug 241435 ***

Thank you! Is there an estimate to when it gets rolled out to iOS, or just "at some point"?