Reftest passes reach 420 of 490
Table layout fixes lift the recorded reftest pass rate to 85.7%. The remaining 71 failures are mapped to structural targets such as nested columns and large-font paint fallback.
Overview
Upstream reftest pass rate climbed from 76.7% to 420/490 (85.7%), with a table-layout milestone — row-height distribution, border-collapse sync, column visibility:collapse — breaking the 81.0% plateau. Incremental wins are now exhausted: the 71 remaining failures were re-scanned and mapped to structural targets, led by nested multicol collapse and the large-font paint fallback deadlock.
Completed
Upstream reftest pass rate up from 76.7% to 420/490 (85.7%): float and clearance refinements, table row-height distribution and border-collapse sync, viewport units and percentage max-height, absolute positioning against the initial containing block, CSS absolute length units, flexbox order.
Table milestone R87–R91 broke the 81.0% plateau: row-height distribution (CSS 2.1 §17.5.3), IFC skip for table cells preserving vertical-align, bilateral border-collapse sync, table-column visibility:collapse, pushing the pass rate to 405/490.
Phase A Final Inline Layout Pass infrastructure enabled: layout now emits inline geometry (font sizes, baselines, letter-spacing, margins) that paint consumes instead of re-running the inline formatting context.
Failure landscape fully mapped (R118, 419/490): all remaining failures are structural — nested multicol collapse traced to zero-height inline children (R121), large-font cluster confirmed as a three-way deadlock between storage box, paint box, and font metrics (R125).
In progress
Next round pivots to a structural target: the R113 two-pass multicol rework (writing IFC per-line heights back into LayoutBox before column distribution), writing-mode vertical-axis float/clearance parameterization, or the large-font deadlock through Phase A IFC path unification.
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.