This bug tracks enabling lazy image loading by default in WebKit trunk, once it seems ready.
I'm not sure it's ready to be turned on yet, but this is a bug to track for when it's ready.
<rdar://problem/59700020>
With the dependencies for this bug now closed (200764, 203557, 207901, 208119), is there a good chance loading=lazy might be turned on by default soon?
Created attachment 441235 [details] Patch
Comment on attachment 441235 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=441235&action=review > Source/WTF/Scripts/Preferences/WebPreferencesExperimental.yaml:694 > - default: false > + default: true Is this tested? > Source/WTF/Scripts/Preferences/WebPreferencesExperimental.yaml:698 > - default: false > + default: true I think you want to leave this off by default. It only applies in some weird situations (maybe the fake Page associated with SVG images or something).
Created attachment 441268 [details] enable lazy image load for webkit
Created attachment 441289 [details] enable lazy image load for webkit
Committed r284228 (243037@main): <https://commits.webkit.org/243037@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 441289 [details].
It seems this patch enabled `IsSameSiteStrictEnforcementEnabled` instead of `LazyImageLoadingEnabled`. $ git show --pretty=oneline 30c67adc54a265473c4fd44bbab6702e9be4487a -- Source/WTF/Scripts/ at 11:39:12 30c67adc54a265473c4fd44bbab6702e9be4487a Enable lazy image loading by default https://bugs.webkit.org/show_bug.cgi?id=208094 diff --git Source/WTF/Scripts/Preferences/WebPreferencesExperimental.yaml Source/WTF/Scripts/Preferences/WebPreferencesExperimental.yaml index 0266e84653..d9e36c19ed 100644 --- Source/WTF/Scripts/Preferences/WebPreferencesExperimental.yaml +++ Source/WTF/Scripts/Preferences/WebPreferencesExperimental.yaml @@ -700,7 +700,7 @@ IsSameSiteStrictEnforcementEnabled: WebKitLegacy: default: false WebKit: - default: false + default: true WebCore: default: false Notice @@ -700,7 +700,7 @@ IsSameSiteStrictEnforcementEnabled:
You're right. The patches look correct. I wonder if this was a merge issue by commit-queue.
Created attachment 442718 [details] Patch
Seems like something that needs a manual commit!
Committed r284995 (243641@main): <https://commits.webkit.org/243641@main>