First, what is the current Intersection Observer API? it allows to detect if a particular HTML element is currently exposed in the visible viewport of the browser w3c.github.io/IntersectionOb…
1
1
1
0
Its use cases includes lazy loading images, fast scrolling for dynamic lists and detection of ad visibility. With the exception of Safari, it's available across all the modern browsers developer.mozilla.org/en-US/… and there is an active @webkit bug on this bugs.webkit.org/show_bug.cgi…
1
2
It's already widely used on the Web, with 20%+ of page loads e.g. in Chrome making use of it chromestatus.com/metrics/fea…
1
1
The demo of the #w3cdevs2018 meetup will be for features under consideration for a next version of the API: it would extend the current API to provide a strong guarantee that a particular #HTML element is completely visible and unmodified

Sep 25, 2018 · 4:30 PM UTC

1
1
1
The primary motivation is to eliminate common patterns of fraud and abuse on the Web, #clickjacking in particular, and to enable trust relationships between embedded third-party iframes and their host documents
1
Specifically, it gives the iframe a strong guarantee that its content is visible on screen, and has not been painted over or altered in any way by the embedding document.
1
Come discover this cool demo presented by Stefan Zager (@google). The #w3cdevs2018 meetup is free and open to all, you just need to register! ti.to/w3c/w3c-developer-meet…