Tagged “chromium”
-
Container Timing: moving to Origin Trial
Container Timing is entering Origin Trial in Chromium 148–153, opening real-world testing for early adopters. Learn how to register, what feedback we need, and what to expect at BlinkOn 21.
-
The implementation of Container Timing: aggregating paints in Blink
Deep dive on the implementation details of the Container Timing API for Chromium. How we track the paints? How we buffer the data for each component?
-
Container Timing: measuring web components performance
An introduction to Container Timing, a new web performance API that lets developers measure when complex components finish painting and shows how to use its native implementation now available behind a Chromium feature flag.
-
Maintaining Chromium downstream: how can upstream help?
How Chromium upstream can assist downstreams via better componentization, extensibility, and downstream advocates.
-
trace-chrome: easy remote tracing of Chromium
Introduces trace-chrome, a NodeJS CLI tool for lightweight remote Perfetto trace capture from Chromium on embedded devices via remote debugging port, avoiding UI overhead; supports categories, memory dumps, and easy installation via npx or npm.
-
Maintaining Chromium downstream: keeping it small
Strategies for maintaining a Chromium downstream project by minimizing codebase delta through metrics tracking, frequent updates, and upstream contributions to ease rebasing amid rapid changes.
-
Maintaining Chromium downstream: update strategies
Outlines rebase vs. merge for integrating upstream changes, recommends frequent small updates tied to Chromium's main/beta/stable cycle, and stresses automation/testing for daily tracking while minimizing delta size.
See all tags.