FreeType and Taffy improve rendering results
FreeType becomes the default rasterizer and Taffy upgrades from 0.7.7 to 0.12.1. Font alignment and layout fixes increase WPT rendering passes.
Overview
FreeType rasterization became the default renderer and the default fonts were aligned with Chromium's font wall, which alone gained about +200 CSS2 WPT passes on retest. The vendored taffy layout engine was upgraded from 0.7.7 to 0.12.1, and a steady stream of zero-regression layout fixes landed across floats, br, grid and clearance handling.
Completed
Flipped the FreeType rasterizer on by default (+232 oracle passes, zero regressions); aligning the initial/sans-serif fonts with Chromium (Liberation Serif/Sans) then gained about +200 CSS2 passes on retest.
Vendored taffy upgraded 0.7.7 → 0.12.1 (M1–M5) with native float coexistence, a fresh Chromium-150 oracle baseline, and oracle capture against non-headless Chromium.
Landed a batch of zero-regression layout fixes: br line-height struts (+28), CSS Grid default justify-content: stretch (+10), CSS2.1 §8.3.1 clearance containment, IFC skipping out-of-flow boxes, width:min-content intrinsic sizing, and position:fixed bottom/right viewport insets.
Shipped the first vertical-mode table slices (axis transpose, colspan/rowspan, row-extras, vrl caps) and the first multicol nested-spanner wrapper fragmentation (+3 flips), plus text-autospace and font-size-adjust property support.
In progress
Multicol is the main open front — the first nested-spanner fragmentation landed and the section-height model is being re-derived from fresh ground truth, while the L2 clearance/collapse-through cluster follows a multi-session roadmap and floats-006 Phase A (five-way coordination) is queued.
Sources
Engineering guides
How ZeroWeb tests AI-autonomous software engineering
A browser gives AI development a long-running test case: architecture, code, debugging and verification must work together.
ZeroWeb Rust browser architecture: from request to pixels
Follow the page pipeline and the boundaries between the browser application, embeddable WebView, engine and rendering infrastructure.
Getting started with ZeroWebView and ZeroBrowser
Prepare a local checkout, launch the desktop browser and inspect the WebView API before embedding the experimental engine.
How to read ZeroWeb WPT and performance results
Understand self-source reftests, assertion-based suites, changing corpus sizes and p95 benchmarks before comparing results.