Conversation
The parser appends attributes one at a time, so `<video src loading=lazy>` reached the resource selection algorithm with `loading` still absent, was treated as Eager, and delayed the load event until the video was scrolled into view. Fixes #12854. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
zcorpan
added a commit
to web-platform-tests/wpt
that referenced
this pull request
Sep 22, 2026
For whatwg/html#12970 (fixes whatwg/html#12854). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The parser appends attributes one at a time, so
<video src loading=lazy>reached the resourceselection algorithm with
loadingstill absent, was treated as Eager, and delayed the load eventuntil the video was scrolled into view.
Fixes #12854.
loadingattribute (Add support for video and audio element lazy-loading via the loading attribute #11980); Chromium already behaves this way.loadingon media elements isn't implemented yetloadingon media elements isn't implemented yet(See WHATWG Working Mode: Changes for more details.)