Hi Tobias, Very exciting! This is a _very_ welcome addition to the family of Web APIs, IMHO.
I’m curious about the performance characteristics for consumers of this API: how does it scale in respect to 1. The amount of observers active on a single page and 2. Size of the page in raw DOM node count, e.g. the single-page WHATWG HTML5 spec? Thanks, Mike. > On 15 Mar 2017, at 06:30, Tobias Schneider <tschnei...@mozilla.com> wrote: > > As of March 14 I intend to turn the IntersectionObserver API on by default > on all platforms. It has been developed behind the > dom.IntersectionObserver.enabled > preference. Chrome is already shipping it since 51. > > Manual QA and fuzzing was successfully completed ( > https://wiki.mozilla.org/QA/IntersectionObserver). A telemetry experiment > run for 7 days, enabling the feature for 10% of our nightly (54 and 55) > user population. No crashes or stability issues related to this feature > occurred during that time. > > *Bug to turn on by default*: https://bugzilla.mozilla.org/show_bug.cgi?id= > 1321865 > *Link to standard*: https://wicg.github.io/IntersectionObserver/ > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
