Bug 264864
| Summary: | Use scrollMargin for lazy load intersection observer | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Traian Captan <tcaptan> |
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | bfulgham, johannes.odland, johannes.odland, simon.fraser, webkit-bug-importer, zalan |
| Priority: | P3 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=263370 | ||
Traian Captan
Currently the lazy load intersection observer is set up using a rootMargin. This does not work well for pages that use images in CSS scrollers, like carousels, causing the images to load too late, when they become visible and the intersection with the root is detected. To work around this issue some developers are choosing to not use lazy loading, thus increasing the overall bandwidth usage for their sites.
This problem was discussed in issue 431(https://github.com/w3c/IntersectionObserver/issues/431).
Using scrollMargin for the lazy load intersection observer will allow lazy loading images to load when they are near the viewport as expected.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/118706766>
Simon Fraser (smfr)
*** This bug has been marked as a duplicate of bug 263370 ***
Johannes Odland
@smfr This bug is not quite the same as 263370, as this bug relates to using scrollMargin for lazy loading.
I'm planning to file a separate PR for this once/if https://github.com/WebKit/WebKit/pull/40687 lands.
Simon Fraser (smfr)
Mistaken duplication.
Johannes Odland
Pull request: https://github.com/WebKit/WebKit/pull/43712
EWS
Committed 293552@main (19ed0f7d93d1): <https://commits.webkit.org/293552@main>
Reviewed commits have been landed. Closing PR #43712 and removing active labels.