Chrome 147 adds loading attribute to audio/video behind flag

[tunetheweb]

Summary

We're adding loading=lazy to <audio> and <video> attributes!

Coming to Chrome in 147 (behind a flag): https://chromestatus.com/feature/5200068565139456

FYI: @scottjehl @hjanuschka

Test results and supporting details

Audio:
https://wpt.fyi/results/html/semantics/embedded-content/the-audio-element?label=experimental&label=master&aligned

Video:
https://wpt.fyi/results/html/semantics/embedded-content/the-video-element?label=experimental&label=master&aligned

https://chromestatus.com/feature/5200068565139456

Implementation bugs:

• Chrome: https://crbug.com/469111735 -
• Firefox: https://bugzil.la/2005072 (being implemented at: https://phabricator.services.mozilla.com/D278547)
• Safari: https://webkit.org/b/303995 (being implemented at: Implement HTML video and audio element lazy-loading via the loading attribute WebKit/WebKit#58220)

Firefox and Safari implementations are being actively worked on but, as per policy, I've left this marked as "experimental" until two implementations land in stable.

More details:

• https://scottjehl.com/posts/lazy-media/ (with a demo of it working)
• https://www.januschka.com/chromium-video-lazy-loading.html

Related issues

See spec updates here: whatwg/html#11980.

Content PR: mdn/content#43434

Makes progress on: mdn/mdn#809

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[tunetheweb]

Pardon my ignorance @caugner what does "auto-merge" mean here?

Does @hamishwillee need to approve as he's on the approver list as was looking earlier?

Or is it cause it's outdated? the "Update branch" button returns an error for me (apparently because auto merge is enabled!) :-(

[caugner]

@tunetheweb This looks like a GitHub bug. Can you merge main and push? Hopefully that resolves the issue.

[tunetheweb]

@tunetheweb This looks like a GitHub bug.

Been an increasing number of them lately!

Can you merge main and push? Hopefully that resolves the issue.

Done. Though looks in an even weirder state now 😔 Will keep an eye on it and see if it resolves itself. Worst case I'll open a new PR from a new branch if I have to!