Iframe lazy loading is now being shipped in 121. Bug to enable
<https://bugzilla.mozilla.org/show_bug.cgi?id=1860729>.

On Thu, Oct 19, 2023 at 4:55 PM Oliver Medhurst <[email protected]>
wrote:

> This has just been delayed a cycle (now likely Firefox 121 instead of 120)
> due to some bugs found in Nightly. Remaining enabled in Nightly but not
> beta or release yet.
>
> On Wed, Oct 18, 2023 at 3:10 PM Oliver Medhurst <[email protected]>
> wrote:
>
>> As of today (Firefox 120), I intend to turn on iframe lazy loading by
>> default on all platforms. It has a flag (dom.iframe_lazy_loading.enabled),
>> but it is being enabled by default in the same implementation patch as it
>> is a low-risk feature and we pass web platform tests. Chromium and WebKit
>> already ship it at this time.
>>
>> Summary:
>> Lazy loading iframes (<iframe loading=lazy>) allow websites to defer
>> loading an iframe until it is in view to speed up first page loads and
>> reduce initial network usage by specifying the element's loading attribute
>> as "lazy". We have supported lazy loading images since Firefox 75.
>>
>> Bug: https://bugzil.la/1622090
>> Specification: https://html.spec.whatwg.org/#attr-iframe-loading
>> Standards body: WHATWG (HTML)
>> Platform coverage: All
>>
>> Preference: dom.iframe_lazy_loading.enabled (on by default)
>> DevTools bug: None
>> Standards position:
>> https://github.com/mozilla/standards-positions/issues/840
>>
>> Other browsers:
>> - Blink: Shipped since Chrome 77
>> - WebKit: Shipped since Safari 16.4
>>
>> Web platform tests:
>> https://wpt.fyi/results/html/semantics/embedded-content/the-iframe-element?q=lazy
>> (I also plan to add more for edge cases in the patch and future)
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAKxzt6a7G_uMnV8RS2-nv8yH%2Bapvu5bMSQfK3dgNwoR-E%2Bx%2BSg%40mail.gmail.com.

Reply via email to