CDP and DevTools goals close
DevTools now operates the real browser, and the CDP gate checks 33 deterministic steps. Vertical writing and multi-column fixes lifted rendering passes above 15,000; a layout slowdown was also recorded.
Overview
Two developer-tools goals went from charter to Done this week. cdp-protocol closed on 09-16 with user sign-off; devtools followed a day later. The DevTools frontend now drives the real browser: Elements with live DOM, a working Console REPL, a Network panel whose event shapes were validated against a real Chrome capture, an Application cookie panel, and a GUI-mode CDP server that opts in via --remote-debugging-port.
After closing, the CDP gate settled into silent monitoring, re-running 33 deterministic green steps day after day (that's the 1,300+ ledger commits). On the rendering side the vertical writing-modes campaign and a multicol push moved the corpus past 15,000 on 09-18, ending the week at 15,148 of 16,594 (91.31%, up from 89.0% last week).
The row-progression cluster closed 12/12 with ten pixel-perfect cases, the ruby overhang model went default-on, multicol climbed from 288 to 316 passing cases, and background-clip:text got a constant-color paint path worth seven more green cases. One regression was filed, honestly: the low-frequency guard measured page-level layout 5.24× slower on its morning page (1.27× on medium, paint +10-11%), specific to the layout stage and suspected in this window's vertical/multicol work.
Absolute budgets still hold; the bisect is pending.
Completed
cdp-protocol reached Done on 09-16 with a user-approved branch-B finalization. The goal had started on 09-12 with three CDP commands and a Playwright connect that failed; it ended with a 33-step deterministic e2e matrix and a frozen M5 scope. The frames.click+evaluate case is the one acknowledged gap and the only outstanding obligation. Since closure the stream has run silent-monitoring rounds, re-running the gate daily against the same tree and staying at 33 green.
devtools reached Done on 09-17 (DC-1~3). M0 pinned the official devtools-frontend bundle and served it over /devtools/ with /json discovery and per-tab devtoolsFrontendUrl. M1 wired per-page WebSocket routing, live-DOM Elements, a Console REPL (the -32601 errors went to zero) and a Computed style sidebar.
M2 built the Network panel on a subscription-broadcast event model, added the Application cookie panel, and aligned request-event shapes against a real Chrome capture; a clean bisect proved the mismatch was on ZeroWeb's side and it got fixed. M3 exposed a GUI-mode CDP server behind --remote-debugging-port (loopback only, off by default), and all Done Criteria checked. GUI tab bridging is logged as a cross-stream coordination item, not a goal defect.
Vertical writing modes took the biggest share of the week (~170 commits). The corpus broke 15,000 with the vertical inline-block fix (R4460) and crossed 90% at R4467. The row-progression cluster closed 12/12 at pixel-perfect 0.00% (R4480: vertical table rowspan extension plus the vertical-cell storage exception).
Also landed: vertical glyph depth compensation (+0.8em anchor, taking inline-table-alignment's 4 cases to 0.00%), central baseline assembly for vertical IFC, taffy location frame normalization for vertical containers, and the 5.5 shrink coordinate split. The ruby overhang model flipped default-on at R4422, once its gate-scoped rounds went green with zero new reds.
Multicol work (R4495-R4524) took css-multicol from 288 to 316 passing. The balance-height symmetric write-back (R4508, +11), inseparability minimums, shrink-sibling restack, the bordered-wrapper region×column fragmentation model, data-driven span-all bg strips and nested-multicol child clipping each closed cases. The spanner-margin cluster took two rounds of honest negative results before the real cause surfaced: a phantom inline-block height on the reference side.
Paint-side clip work (R4525-R4552) gave background-clip:text a constant-color paint path. When the background is one solid color, glyph pre-blending is mathematically equivalent to mask compositing, so no offscreen pass is needed; five cases went green immediately, and seven in total after the ancestral-chain round fixed a stacking-context/deferred-paint double-fork. corner-shape gained overflow inner-shape clipping. Corpus peaked at 15,148/16,594 = 91.31%.
css-text and fonts (R4349-R4385): background shorthand multi-layer with per-layer origins, scripted scrollTop/scrollLeft end-to-end, text-transform multi-value parsing effective on flattened inline runs (a 161-case family to all green), the font fallback chain's vertical metrics wired default-on, CJK contiguous line-breaking default-on (+27), and list-marker baselines synced with layout struts.
CI and measurement: CI-GUARD round 30 delivered the first all-green 11/11 run with benchmarks passing since round 28. Round 33 watched a fresh runner pool (epyc-9v45) auto-create its baseline at 0.60× the old 7763 budgets. Round 34 then confirmed the benchmarks family running red again on yet another new platform (6973p), and the stale-platform re-capture consultation was widened. The weekly WPT trend (09-19) recorded 14,693/16,058 = 91.5% upstream reftest on the CI-side corpus.
In progress
The regression guard filed this week's one open incident. Across the 143-product-commit window, page-level layout ran 5.24× slower on the morning page (1.27× medium, 1.26-1.29× welcome, paint +10-11%). The A/B interleaved attribution pins it to the layout stage specifically, with the vertical/multicol work as the suspect set. A shared-window load wave polluted the bisect runs, though, so conviction waits for a quiet window and the owning stream's own slot.
Absolute budgets are not breached (morning 20.5ms vs 47.83ms). Rendering-compat's remaining ledger: 136 css-multicol deep-domain fails, five background-clip:text residuals (blend×mask pipeline, URL color constancy, flex, SC propagation, scroll), the ≥10%-diff band re-survey (161 cases, multicol-span-all flagged as the biggest single lever), and the real mask pipeline RFC v2. devtools is in custody mode; cdp-protocol holds the frames.click+evaluate obligation until subframe capability lands.
Benchmarks re-capture for the drifted platforms (7763/9v74/6973p) remains with the user.
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.