[Webkit-unassigned] [Bug 159475] New: Implement IntersectionObserver support

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=159475

            Bug ID: 159475
           Summary: Implement IntersectionObserver support
    Classification: Unclassified
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: All
                OS: All
            Status: NEW
          Severity: Enhancement
          Priority: P2
         Component: Frames
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jeffreytgilbert at gmail.com

Working draft for implementation:
https://wicg.github.io/IntersectionObserver/

Intent to implement in Firefox by version 50
https://bugzilla.mozilla.org/show_bug.cgi?id=1243846
https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API

Chrome adopted IntersectionObserver support in version 51
https://www.chromestatus.com/feature/5695342691483648 
https://chromium.googlesource.com/chromium/src/third_party/+/master/WebKit/Source/core/dom/IntersectionObserver.cpp

MS Edge has committed to adopting support, but have not implemented yet
https://developer.microsoft.com/en-us/microsoft-edge/platform/status/intersectionobserver
https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/13407852-intersectionobserver

Rationale:
Advertisements typically use Flash, frame per second counters, or costly geometry calculations within loops to determine if an ad is in view or not. The mechanisms are difficult to implement, non-standardized, and costly to web performance. The IAB, MRC, browser vendors, and web standards bodies have attempted to solve for this by introducing first the PageVisibility 2 API draft, and now splintered off from that, the IntersectionObserver API. This pattern allows for efficient event driven code to take advantage of indicators sent directly from the browser of the area of a page or more importantly sandboxed iframe which are viewable without requiring access to the parent documents information or leaking important security details.

Chrome has introduced this early as a way of hastening the elimination of the Flash browser plugin as a necessary evil, which they plan to throttle by default at the end of the year. Firefox's intention is to introduce this functionality as part of version 50, currently in nightlies. Microsoft has commented to the IAB that they intend to introduce the functionality, but have not committed to a build version or date for releasing it. That leaves only Safari/Webkit based browsers left. This solves an obvious problem for advertisers and consumers/end users who want transparency and performance, respectively.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160706/f76ecf1b/attachment.html>