Chrome's CSS Scroll Snap Implementation: Blink and Compositor Deep Dive
Blink28629 Loka 2025

Chrome's CSS Scroll Snap Implementation: Blink and Compositor Deep Dive

The source provides an extensive technical explanation of the implementation of CSS Scroll Snap within the Google Chrome browser, specifically detailing how the feature is managed across the Blink rendering engine and the Chromium Compositor (CC). It begins by outlining the historical evolution of scroll snapping from early coordinate-based specifications to the modern element-based model, which uses properties like scroll-snap-type and scroll-snap-align. The text then describes the division of labor: Blink handles the interpretation of CSS and calculates precise snap coordinates (SnapContainerData), while the Compositor thread utilizes this data along with various SnapSelectionStrategy objects to manage smooth scroll animations, handle user input, and ensure correct snapping behavior (including managing the 50% proximity threshold and scroll-snap-stop priority). Finally, the document discusses future developments for the feature, such as the introduction of scroll snap events and potential fine-grained control for developers.


Jaksot(395)

blink::TransformPaintPropertyNode / ClipPaintPropertyNode / EffectPaintPropertyNode / ScrollPaintPropertyNode

blink::TransformPaintPropertyNode / ClipPaintPropertyNode / EffectPaintPropertyNode / ScrollPaintPropertyNode

These are the nodes within those four trees. Every piece of painted content (a “paint chunk”) is associated with a tuple of (Transform, Clip, Effect, Scroll) nodes—its PropertyTreeState. This precisel...

10 Loka 202533min

blink::PaintPropertyTreeBuilder

blink::PaintPropertyTreeBuilder

builds/updates paint property trees.Consumes the layout/fragment data and produces the four paint property trees (Transform, Clip, Effect, Scroll) for the current frame. These trees encode coordinate ...

10 Loka 202547min

blink::PrePaintTreeWalk

blink::PrePaintTreeWalk

cross‑frame pre‑paint traversal. Runs in the InPrePaint lifecycle phase. Walks the entire layout tree starting at the root LocalFrameView, updating paint invalidation state and computing the context n...

10 Loka 202531min

blink::NGPhysicalFragment and friends

blink::NGPhysicalFragment and friends

Layout takes the styled DOM and produces a fragment tree of positioned boxes. In modern Blink this is LayoutNG; the core artifact is NGPhysicalFragment, which stores geometry and is used downstream fo...

10 Loka 202537min

blink::StyleEngine

blink::StyleEngine

style invalidation & resolution (recalc). 
Given DOM/style changes since the last frame, StyleEngine computes updated ComputedStyles, manages active stylesheets/media query state, and marks the right ...

10 Loka 202534min

blink::Document & blink::DocumentLifecycle

blink::Document & blink::DocumentLifecycle

states that gate phases. The document owns the DOM and keeps a DocumentLifecycle state machine that ensures we do things in phase order (style before layout, pre‑paint before paint, etc.). Lifecycle t...

10 Loka 202535min

blink::LocalFrameView

blink::LocalFrameView

orchestrates style → layout → pre‑paint/paint for a frame. This is the workhorse that actually runs lifecycle phases. On a frame tick from WebFrameWidgetImpl, it goes through style recalc, layout (Lay...

9 Loka 202544min

blink::LocalFrame

blink::LocalFrame

the document host and local‑root boundary.
The local frame owns the Document and its LocalFrameView. The local root frame coordinates lifecycle for its subtree (including OOPIF boundaries handled late...

9 Loka 202532min