Canvas fixes and QuickJS DOM bindings
Canvas path-object failures were cleared and most image-drawing gaps addressed. QuickJS native DOM binding slices completed, with page zoom and device-DPI frames added to the browser.
Overview
The Canvas 2D WPT sweep cleared the last path-objects failures and most of the drawing-images gaps. The QuickJS native DOM binding line finished M6 S0q-S5q and closed the S1q composite objects. The HTML behavior compatibility track, started this week, completed M0-M4, and browser product work added page zoom and device-DPI compositor frames.
Completed
Canvas: path-objects reached 202/0 (adaptive bezier subdivision, zero-length stroke pruning, roundRect spec start point, arc annulus, nonzero/evenodd fill rules). drawing-images is down to one failure left. f16 pixel storage with linear color space, display-p3 management, CanvasFilter (13/13 filters), GIF first-frame decoding, and colorMatrix filter went in too.
QuickJS native DOM bindings: M6 S0q-S5q all landed — EventTarget with three-phase capture/bubble, DOMException error paths, customElements five-piece with lifecycle, observedAttributes; S1q closed with attributes/classList/dataset composite objects.
HTML behavior compatibility track (launched 08-12): M0-M4 completed — shared action transaction core, single-process form POST navigation, anchor navigation intents, live renderer WebDriver + WPT testdriver.
Browser product layer: Chrome-style page zoom, compositor frames at device DPI, chrome controls and address bar polish, frozen HTML5test browser smoke coverage.
In progress
Canvas drawing-images has one failure left (nonexistent). QuickJS M6 depth items remain: weak/finalizer GC, Event/DOMException constructor instanceof, and whenDefined pending. Turning V8 native bindings on by default still awaits a user decision. Rendering and font stack slices plus browser-shell productization continue.
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.