Cool, makes sense to me! Thanks for working on it Helmut!

Rick

On Thu, Feb 5, 2026, 1:58 p.m. Helmut Januschka <[email protected]>
wrote:

> *Contact emails*
> [email protected]
>
> *Explainer*
> https://github.com/whatwg/html/pull/11980
> https://chromium-review.googlesource.com/c/chromium/src/+/7511253
> https://issues.chromium.org/issues/469111735
>
> *Specification*
> https://github.com/whatwg/html/pull/11980
>
> *Summary*
> Adds the loading attribute to <video> and <audio> elements, allowing
> developers to defer media resource loading until the element is near the
> viewport using loading="lazy". This matches the existing lazy loading
> behavior for <img> and <iframe> elements, improving page load performance
> and reducing data usage. CL:
> https://chromium-review.googlesource.com/c/chromium/src/+/7511253
>
> *Blink component*
> Blink>Media
> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EMedia%22>
>
> *Web Feature ID*
> Missing feature
>
> *Motivation*
> Web developers frequently need to defer loading of video and audio
> resources to improve page load performance and reduce data usage,
> especially on pages with multiple media elements below the fold. Without
> native support, developers must implement custom JavaScript solutions using
> Intersection Observer to detect when media elements enter the viewport and
> then dynamically set the src attribute. This approach is error-prone, adds
> complexity, and cannot integrate with the browser's preload scanner. The
> loading attribute already exists for <img> and <iframe> elements, and
> developers expect the same declarative API for media elements. Native lazy
> loading allows the browser to optimize resource loading with network-aware
> thresholds, properly handle the interaction with autoplay and preload
> attributes, and avoid blocking window.onload for offscreen media.
>
> *Initial public proposal*
> https://github.com/whatwg/html/pull/11980
>
> *Requires code in //chrome?*
> False
>
> *Tracking bug*
> https://issues.chromium.org/issues/469111735
>
> *Measurement*
> UseCounters should be added to track adoption
>
> *Estimated milestones*
>
> No milestones specified
>
>
> *Link to entry on the Chrome Platform Status*
> https://chromestatus.com/feature/5200068565139456?gate=5103036932423680
>
> This intent message was generated by Chrome Platform Status
> <https://chromestatus.com/>.
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFmjHKSFVWGyOWV%2BKymVmsaro9YbXoN5YYGbnNpnLo1KLe4dCQ%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFmjHKSFVWGyOWV%2BKymVmsaro9YbXoN5YYGbnNpnLo1KLe4dCQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY-7p4kU5eYeWE9kM1k6rhX4GR7tAwTT8Fd%3DCCOC80D0kw%40mail.gmail.com.

Reply via email to