blink::PaintController
Blink28610 Loka 2025

blink::PaintController

builds the display list + paint chunks and manages caching.

As painters call into GraphicsContext, they also drive a PaintController which groups drawing into display items and paint chunks (each keyed by the current property‑tree state). It also handles reuse of cached items to avoid repaint when nothing visually changed. Output is an immutable PaintArtifact. (Chromium Git Repositories)

Key fields

  • PaintArtifact* new_paint_artifact_ — being built for this frame;

  • PaintArtifact* old_paint_artifact_ — previous frame for cache matching;

  • PaintChunker paint_chunker_ — forms chunk boundaries based on property state;

  • PaintControllerPersistentData* persistent_data_ — holds prior artifact & subsequences. (Chromium Git Repositories)

Most important methods

  • UpdateCurrentPaintChunkProperties(const PropertyTreeStateOrAlias&) — starts/updates the current chunk when property state changes. (Chromium Git Repositories)

  • template <class T> CreateAndAppend(...) — appends a display item (records drawing op + metadata). (Chromium Git Repositories)

  • bool UseCachedItemIfPossible(...) — reuses prior items to skip repaints. (Chromium Git Repositories)

  • void BeginFrame(const void* frame) / FrameFirstPaint EndFrame(const void* frame) — delimit a painting pass for metrics + cache book‑keeping. (Chromium Git Repositories)

  • (Internals also maintain id→index maps to support O(1)/linear cache lookups.) (Chromium Git Repositories)

Hands off to: the PaintArtifact it produces.


Jaksot(397)

cc::LayerTreeHost in Chromium's Compositor

cc::LayerTreeHost in Chromium's Compositor

The source provides an extensive technical explanation of the cc::LayerTreeHost class, which acts as the central main-thread component in the Chromium compositor architecture. It details how this comp...

20 Syys 202537min

cc:: Scheduler / SchedulerStateMachine

cc:: Scheduler / SchedulerStateMachine

Drives the frame loop on the compositor thread (BeginFrame → Animate → Commit → Draw), deciding when to ask Blink for a new frame or to draw with existing state.

20 Syys 202548min

Chrome Interactions Team: Key Class Reference

Chrome Interactions Team: Key Class Reference

The sources provide an extensive reference guide detailing the key classes and infrastructure involved in handling user interactions—specifically scrolling, gestures, and input—within the Blink and Ch...

20 Syys 202553min

Essential Unix, Git, and Development Commands

Essential Unix, Git, and Development Commands

This comprehensive reference document provides an essential overview of commands used in a Unix-like environment, primarily focusing on Linux/macOS command-line operations and the specialized workflow...

20 Syys 202541min

Chromium and Blink Developer Command Reference

Chromium and Blink Developer Command Reference

The collection of sources provides a comprehensive guide to developing within the Chromium project, focusing heavily on command-line tools and workflows essential for engineers, particularly those wor...

19 Syys 202543min

Chrome Interaction Systems: Scrolling, Animations, and Input

Chrome Interaction Systems: Scrolling, Animations, and Input

The source material provides a detailed examination of Chrome’s architecture and how it manages user interactions like scrolling, animations, and input handling to ensure web pages feel smooth and res...

19 Syys 202526min

The History of the Web

The History of the Web

The source provides an extensive transcript from a YouTube video titled "The history of the web (Chrome University 2019)," featuring a presentation by Chris Wilson from Chrome for Developers. Wilson o...

19 Syys 202526min

Chromium Blink Remote Linux Development Workflow

Chromium Blink Remote Linux Development Workflow

The source provides a comprehensive guide for experienced C++ developers on setting up a development workflow for Chromium's Blink rendering engine, specifically focusing on the core component within ...

19 Syys 202542min