Changes the lazy load intersection observer's init dictionary to use a scrollMargin instead of a rootMargin. This allows lazy loading iframes contained inside CSS scrollers, like carousels, to load as expected when near the viewport instead of the current behavior where these iframes load when at least one pixel is intersecting the viewport.
Overall low as scroll margin also applies to the root element thus not affecting lazy loading iframes that are currently loading with just a root margin.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
The following tests are testing this feature: https://wpt.fyi/results/html/semantics/embedded-content/the-iframe-element/iframe-loading-lazy-in-scroller.html?label=master&label=experimental&aligned https://wpt.fyi/results/html/semantics/embedded-content/the-iframe-element/iframe-loading-lazy-in-scroller-far.html?label=master&label=experimental&aligned https://wpt.fyi/results/html/semantics/embedded-content/the-iframe-element/iframe-loading-lazy-in-scroller-horizontal-far.html?label=master&label=experimental&aligned https://wpt.fyi/results/html/semantics/embedded-content/the-iframe-element/iframe-loading-lazy-in-scroller-horizontal.html?label=master&label=experimental&aligned https://wpt.fyi/results/html/semantics/embedded-content/the-iframe-element/iframe-loading-lazy-in-scroller-nested-2.html?label=master&label=experimental&aligned https://wpt.fyi/results/html/semantics/embedded-content/the-iframe-element/iframe-loading-lazy-in-scroller-nested-3.html?label=master&label=experimental&aligned https://wpt.fyi/results/html/semantics/embedded-content/the-iframe-element/iframe-loading-lazy-in-scroller-nested-4.html?label=master&label=experimental&aligned https://wpt.fyi/results/html/semantics/embedded-content/the-iframe-element/iframe-loading-lazy-in-scroller-nested-5.html?label=master&label=experimental&aligned https://wpt.fyi/results/html/semantics/embedded-content/the-iframe-el
No milestones specified