Page execution converges on a shared runtime
Renderer, TabWorker and the WPT runner share one WebView-based page runtime. The browser interface gains themes, persistent settings and improved tab management.
Overview
The renderer, TabWorker, and the WPT runner now converge on one shared page runtime through WebView, replacing three parallel implementations. Around it, the browser chrome got a near-complete redesign pass — theming, persistent settings, tab management, a new app icon — while the oracle-measured rendering compatibility campaign landed another batch of CSS and layout fixes.
Completed
Runtime unification: a new page-runtime crate now serves WPT runner, TabWorker, and the renderer through one WebView-based path, with loading, script-executor, and frame contracts unified; the renderer cut over to WebView+AsyncPageLoad and WPT renders through the shared runtime behind an engine-direct consistency gate.
Nearly all of the browser chrome redesign landed: light/dark/auto theming with OS detection, a settings page, persisted bookmarks and settings, tab context actions, Ctrl+Shift+T restore, and a Windows native title bar that keeps Aero Snap. A new Chrome-style app icon ships with multi-platform build integration.
The oracle-measured compatibility campaign kept landing fixes: SEA fallback line-breaking, control-character placeholders, per-fragment inline backgrounds, missing inherit-keyword branches, calc() in insets and max-lengths, table shrink-to-fit and cell intrinsic sizing, visibility:collapse table rows, caption-side:bottom, and anonymous block boxes for mixed text-plus-block content. A new reftest-oracle subcommand provides an independent reference.
Networking: HTTP/2 is on by default (ZERO_HTTP2=0 opts back to HTTP/1.1), a persistent disk cache with memory and disk tiers, Vary-aware keys, no-cache revalidation and per-origin quota backs page loads, and incognito tabs plus a ZERO_NOPROXY proxy bypass are in.
In progress
The compatibility campaign reconfirmed the same plateau a fourth time — the isolated fixable points are spent, and what remains is structural rendering work that needs coordinated, rather than isolated, changes. The chrome redesign is near-complete with the last polish gaps still open.
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.