The first week delivers a working browser core
The first week connects CSS, layout, CPU/GPU rendering and V8 to a browser shell. The imported set of 514 upstream reftests records a 76.3% pass rate.
Overview
The project went from its first commit on May 30 to a working browser core in one week: CSS parsing through layout to a 13-primitive CPU and GPU render pipeline, V8-backed script execution, and a browser shell app. Mid-week the milestone plan was reworked around rendering compatibility — the new M1-M6 finished at 100% reftest pass, and M10 ended the week with 514 upstream WPT reftests imported at a 76.3% pass rate.
Completed
Launch: first commit on May 30, and the whole original plan (M1-M13) completed within the week — V8 scripting in the WebView, a WASM sandbox with Wasmtime/QuickJS backends, multi-process IPC, a CDP-compatible headless protocol, and a Chrome-style browser shell app.
Rendering core: all 13 primitive types implemented in both CPU and GPU renderers and consumed by the browser; the 685 in-house reftests pass 100% on both paths, including the GPU headless path.
Layout and text: quirks mode, table and multi-column layout, floats with BFC, Grid/Flexbox edge cases; CJK line breaking, rustybuzz OpenType shaping and unicode-bidi RTL text.
Milestone plan reworked and extended: M1-M6 finished at 100% reftest pass, then M7-M10 added GPU rendering, <img> intrinsic sizing, scroll-container paint offsets, clip-path/backdrop-filter/mask-image, and the first upstream WPT reftest imports — 514 tests at a 76.3% pass rate.
In progress
M10 — upstream reftest compatibility — is the active milestone: 514 tests are in at a 76.3% pass rate, and the week's closing commits were still expanding background shorthand, UA default styles and float positioning. The next step is importing more upstream cases and pushing the pass rate up toward M10 completion.
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.