Browser security enforcement reaches acceptance
CSP gained runtime enforcement and violation events, alongside Mixed Content blocking, HSTS registration and a permissions API. The security goal closed with its remaining coverage gaps recorded.
Overview
A quiet week by commit count (705, more than half of it CDP gate ledger entries), but three goals reached their end state. The big one was security-hardening, chartered on 09-12 and finished on 09-25: CSP went from a parsed-but-inert header to runtime enforcement wired through script, style, connect-src, eval, event-handler attributes and img src-set checkpoints, with violation events. Mixed Content gained tiered subresource blocking, HSTS responses register, and navigator.permissions grew a JS face.
The CSP WPT corpus went from 30 green files to 74 of 445 with zero losses (subtests 16.3% → 28.8%), both kill-switches landed default-on after an A/B where both arms scored 19,451/0F identically, and the reftest gate read 691/691. web-api-batch2 also closed this week (09-24) at clipboard 61/73 (83.6%) and fullscreen 132/150 (88.0%, up from 61.7%).
Rendering compatibility spent the rest of the week in custody: a handful of code rounds early on (clip:text url backgrounds, block-axis content sizing, @container style(), video poster frames, a font-size determinism fix) nudged the corpus to 15,175 of 16,594 (91.45%), then the tree went invariant and patrol rounds held it there through Sunday. The weekly WPT trend ticked up to 91.8% (14,748/16,058).
Completed
security-hardening went from charter to Done in one week (09-25, R11 verdict, DC-1~4 all met). M1 imported the WPT corpora and set an honest baseline: 415 CSP files, subtests at 16.3%. At that point the policy engine parsed but nothing enforced at runtime.
M2 then wired enforcement slice by slice: the SPV constructor with meta assembly and script checkpoints plus violation events (M2-s1), style checkpoints covering inline blocks, external sheets and all three hash algorithms (M2-s3), element-face directive scopes with a WPT GET template surface (M2-s4), connect-src blocking with cross-origin attribution for applied stylesheets (M2-s5), eval gating (M2-s6), script-src-attr event-handler gates (M2-s7), and runtime img src-set checkpoints (M2-s8).
Green files went 30→74 with zero losses; the denominator grew to 445 as the corpus expanded; subtests reached 174/604 = 28.8%. M3/M4 added Mixed Content tiered subresource blocking, HSTS response registration, and a navigator.permissions JS face with change events. M5 flipped both kill-switches default-on: the A/B ran both arms at full suite and both scored 19,451 passed / 0 failed, byte-identical; make reftest read 691/691.
web-api-batch2 closed (09-24, M4, DC-1~4 met). clipboard-apis finished at 61/73 subtests (83.6%), with the residue being custom-format and SVG-cluster cases. fullscreen went 61.7% → 88.0% (132/150) through an async state machine, node-removal exit linkage and vendor-prefix aliases. DnD stays excluded pending the host drag-input pipeline, and the goal says so plainly.
Rendering compatibility's code rounds: clip:text now paints url() backgrounds when the fetched image turns out to be a solid color (multiline-background-image went green), block-axis content-keyword sizing flipped two cases and harvested two more (R4557), @container style() got its cheap slice (string equality, not, named containers, nesting), a mask/unmask investigation turned block-decoration pseudo-elements into real boxes, video poster frames paint, wrapper shrink-to-fit stopped recursing past definite widths, and a font-size determinism fix closed out the docs-round-19 batch.
Corpus: 15,175/16,594 = 91.45%. From R4606 onward the stream ran pure custody rounds (through R4832 by Sunday), holding a tree-invariant anchor of 19,451 tests with zero code changes.
Measurement: the weekly WPT trend (09-26) recorded 14,748/16,058 = 91.8% on the CI-side corpus, up from 91.5%. ZRG-2026-09-27-01 found no new regression and noted the window was the first pure-documentation window since the chronic layout filing began (52 commits, zero product code); morning/layout stayed in its band. CI-GUARD round 39 (09-21) recorded benchmarks running red on both platforms in double runs, neither self-fixable; the stale-platform re-capture consultation continues.
In progress
Rendering-compat is holding in custody with a stable corpus, and its open ledger is unchanged: the ≥10%-diff band (136 cases, fragmented across families with no single lever), five corner-shape residuals in deep domains, and the real mask pipeline RFC v2 waiting on a user decision (the wire-format change crosses crate groups). Two standing items await the user: the stale-platform benchmark re-capture (7763/9v74/6973p, now double-confirmed red) and the physical-GPU memory retest, still with no machine assigned.
The ZRG chronic layout filing got its twelfth re-confirmation without closure; morning/layout stays elevated in-band, and attribution to the vertical/multicol window remains unconvicted. cdp-protocol keeps its daily silent-monitoring gate at 33 green and holds the frames.click+evaluate obligation.
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.