v0.1.12313 Aug 2026·Web APIs & DOM

Real Puppeteer drives the engine: connect, open, navigate, evaluate

The WebSocket protocol transport grows the Target and session model, and the result is a genuine first: an unmodified, off-the-shelf Puppeteer - the standard browser-automation library - connects to Floati's from-scratch engine, opens a page, navigates it, and evaluates JavaScript in it, exactly as it would drive the reference browser. puppeteer.connect, browser.newPage, page.goto and page.evaluate all work against the engine over ws://. Every step was driven by an empirical probe: point real puppeteer-core at the app, fix exactly what it complains about, repeat - discovery and attach events, session routing, navigation lifecycle events, isolated-world bookkeeping, and real remote-object handles. One step remains to full element queries: Puppeteer injects a utility script whose modern JavaScript the engine must run faithfully - that is a JavaScript-completeness item with a named work list, not a protocol gap. DevTools moves 38 to 40; overall holds at 51 until that last step lands and external tools can drive elements end to end.

Parity with the reference browser

74overall, as of v0.1.343

Web APIs / DOM surface42

Security architecture66

GPU / graphics acceleration68

DevTools / extensions72

Networking85

Media85

Accessibility85

Real-world site compatibility99

HTML parsing100

CSS parsing + selectors100

Layout: block / flex / grid / tables / writing-modes100

Paint + visual100

JavaScript language100

JavaScript performance (JIT)100

HTML parsing100

What changed 3 changes

Web APIs & DOM	The flattened Target/session model on the ws transport: target discovery and attach events (Target.targetCreated, attachedToTarget with a session id), session-tagged replies and events, and the single-page mapping where creating a page target IS loading a page - Target.createTarget and Page.navigate load straight into the engine session, including data: URLs, with the reply sent before the lifecycle events so a client can associate them.
Web APIs & DOM	The full navigation lifecycle a client waits on, pushed in order: frame started loading, the init lifecycle for the loader, execution contexts cleared and re-created, frame navigated, DOMContentLoaded and load in both classic and lifecycle-event forms, frame stopped loading - plus isolated-world bookkeeping that re-announces a registered utility world after every navigation, which is exactly what a real browser does and exactly what Puppeteer waits for.
Web APIs & DOM	Real remote-object handles in the protocol layer: object and function results are handed out as objectIds a client can pass back as receivers or arguments; callFunctionOn binds the receiver; getProperties, releaseObject, DOM.describeNode and DOM.resolveNode round out the handle lifecycle; and DOM handles carry the node subtype so Puppeteer constructs real ElementHandles. Verified end to end by the probe script shipped in the repo (cdp-puppeteer-smoke.mjs).