w3c/intersectionobserver

Intersection Observer

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 41 minutes ago
Type:Documentation / SpecificationCategory(s):Browsers & ExtensionsDocumentation ToolsWeb Development
Added to GitGenius on September 19th, 2026
Created on June 19th, 2015
Open Issues & Pull Requests: 75 (+0)
GitHub issues: Enabled
Number of forks: 509
Total Stargazers: 3,612 (+0)
Total Subscribers: 122 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.4 days
Mean response time: 248.9 days
90th percentile: 2068.5 days
Tracked items: 9

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 1,409 days
Stale 30+ days: 10
Stale 90+ days: 10

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • needs test (2)
  • TPAC2024 (1)
  • actionable (1)
  • bug (1)
  • needs spec (1)
  • polyfill (1)
  • tpac2017 (1)
  • v2 (1)

Most active issues this week

Detailed Description

Intersection Observer is a web standard specification that defines an API for detecting when elements enter or leave the viewport or a specified container.

The specification addresses the problem of efficiently detecting element visibility without expensive layout calculations. Rather than requiring developers to manually track scroll events and compute element positions, Intersection Observer provides a native browser mechanism where observers asynchronously notify a callback when a watched element's visibility state changes relative to a viewport or root element. This approach offloads the computational work to the browser, which can optimize it at the rendering level.

Developers should adopt this specification when building features that depend on element visibility, such as lazy-loading images, infinite scroll pagination, or analytics tracking. The tool suits any project targeting modern browsers, as the API has shipped across all major browser engines. Since native implementations are now widely available, the specification itself serves as the authoritative reference rather than as a polyfill or library to install.

The specification is maintained as a W3C standard document written in Bikeshed format. Development activity centers on maintaining the formal specification text and ensuring alignment with browser implementations that have already shipped across the platform.