Chrome screenshots become the rendering reference
Pixel comparisons now use real Chrome screenshots. All ten upstream WPT CSS directories were imported, and the first results guide rendering fixes.
Overview
The compatibility program rebuilt its measurement: every reftest is now pixel-compared against real Chrome screenshots instead of ZeroWeb's own output. The full upstream WPT CSS corpus — all ten directories, ending with the huge CSS2 — was imported, and the first results already steered a new wave of rendering fixes.
Completed
Built a Chromium screenshot oracle: every reftest is pixel-compared against real Chrome output, replacing self-referential pass rates with honest cross-browser numbers — the first full sweep found 46.5% of previously self-passing tests disagreed with Chrome.
Imported the entire upstream WPT CSS reftest corpus — grid, position, tables, text-decor, fonts, flexbox, multicol, writing-modes, text, and finally CSS2, the largest directory at ~13k files and over 6,000 test/reference pairs — with recursive discovery and per-directory oracle capture tooling.
Landed a wave of oracle-driven rendering fixes: min-width/min-height initial value auto, type-aware flex shorthand parsing, table-layout:fixed and colspan column widths, multicol crash guards, and image clip crop semantics.
The reftest path now loads @font-face custom fonts, and the browser's URL-navigation path picks up external stylesheets and <img> subresources, with JPEG/SVG decoding unified into render-foundation.
In progress
The oracle capture for CSS2 — the last and largest directory — was still running as this was written, due to finish the same evening; its cross-validate will close the first full ten-directory baseline, with the aggregate agreement expected to land around 30%. The earlier css-text results already point at precision-sensitive text layout (white-space/text-align) as the next known lever.
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.