Callback steps in "start intersection-observing a lazy loading element" may return too early #10019
Description
What is the issue with the HTML Standard?
The callback steps in this algorithm has the following:
-
For each entry in entries:
-
Let resumptionSteps be null.
-
If entry.isIntersecting is true, then set resumptionSteps to entry.target's lazy load resumption steps.
-
If resumptionSteps is null, then return.
-
^-- here's the bug: If resumptionSteps is null, we will bay early, even if we didn't look at all entries yet.
It seems to me that we should simply "continue" to the next iteration of the loop in this case.