Rendering failures fall to 884
33 previously closed goals were archived, and 15 more reached a terminal state. Rendering fixes reduced full-corpus failures from 1,104 to 884; media timing and browser stability also improved.
Overview
Two batch waves on 10-20 moved 33 already-closed goals into archive/ (18 engineering goals, 15 WPT-domain goals); fifteen more goals reached terminal state this week.
Eight WPT compat goals closed: html-syntax-compat archived at 61,228/61,333 (99.9%); workers-compat went from 169/371 to 693/714 (97.1%) within a day; svg-compat followed its 8.8% M1 baseline (134/1,527) with M4 closure a day later at 1,245/1,772 (70.3%); webgl-compat covered M1→M4 in two days and fixed its baseline at 2,112/2,115 (3 upstream IDL-mixin failures accepted); navigation-compat closed against the M3 criteria (473/584, 81.0%); encoding-compat (12,072/12,075), pointerlock-compat (22/22) and page-wasm (715/719) closed in the same window.
Four engineering goals closed: media-runtime-isolation with all five done-criteria verified (media-process stays default-off), the incremental-rendering oracle (five DCs), background-resource-lifecycle, and compositor animation plus Worker Canvas. devtools and browser-delivery-loop were archived as terminated, clearing the goal root.
On the media side, batch A of plan C landed: sample-level clock alignment moved the media clock rate from 1.45402 to 1.00000; narrowed cue-anchored seek cut the mid-GOP cold path from 302ms to 18ms; source residency gained a 256MB admission-eviction cap.
Rendering cut full-corpus failures from 1,104 to 884 (R5272 accounting: 15,706/16,590, 94.67%): the collapse border model took 001e from 7.25% to 0.00%, ::selection highlight owner and UA-fallback models got several consecutive rounds, clip:text converged box2/3 from 11.71% to 0.00%, and the frame-driven rAF fix lifted 30-second frame counts from 2 to 1,575.
On the browser, the split_important crash on CSS variable values ending with Chinese characters is fixed (#215), CDP eval round-trips dropped from 52ms to 5ms, and a zero://feedback page plus --profile/--version flags landed.
Completed
Two batch waves moved 18 completed goals and 15 closed WPT-domain goals into archive/ (10-20)
html-syntax-compat closed and archived at 61,228/61,333 (99.9%)
workers-compat closed within a day: 169/371 on 10-20 to 693/714 (97.1%) on 10-21, DC-1~4 all met
svg-compat went from its 8.8% M1 baseline (134/1,527) to M4 closure a day later: 1,245/1,772 (70.3%)
webgl-compat covered M1→M4 in two days and was signed off, baseline 2,112/2,115 (3 upstream IDL-mixin failures accepted)
navigation-compat closed against the M3 criteria (473/584, 81.0%); encoding-compat 12,072/12,075, pointerlock-compat 22/22 and page-wasm 715/719 closed in the same window
media-runtime-isolation closed with all five done-criteria verified (media-process stays default-off); incremental-rendering oracle (five DCs), background-resource-lifecycle and compositor animation + Worker Canvas closed the same week
Media batch A landed: sample-level clock alignment moved the rate from 1.45402 to 1.00000; cue-anchored seek narrowing cut 302ms→18ms; source residency gained a 256MB admission-eviction cap
Rendering failures fell 1,104→884 (15,706/16,590, 94.67% at R5272): collapse 001e 7.25%→0.00%, ::selection owner/UA-fallback fixed over consecutive rounds, clip:text box2/3 11.71%→0.00%; after the frame-driven rAF fix, 2→1,575 frames per 30s
Browser: fixed the split_important crash on CSS variable values ending with Chinese characters (#215); CDP eval 52ms→5ms; new zero://feedback page, --profile and --version flags
In progress
rendering-compat has 884 cases left against the 100% target; next up are the selection-image-001 image-selection paint path and the mechanism gaps in partial-line and vertical ::selection highlight. html-semantics-compat reached 63.48% after slice 14 cleared the meter cluster.
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.