v0.1.12413 Aug 2026·Rendering, Web APIs & DOM, DevTools

Puppeteer queries elements end to end - the first floor moves the overall

This is the release the scorecard has been waiting for: the first time a named infrastructure floor is genuinely bridged, so the overall figure moves - from 51 to 52. Real, unmodified Puppeteer now drives the from-scratch engine through a COMPLETE flow: connect, open a page, navigate it, evaluate JavaScript, and - the piece that was missing last release - QUERY ELEMENTS. page.$eval with a CSS selector returns the element's text, exactly as it does against the reference browser. Getting there needed Puppeteer's own injected utility script to run faithfully in the engine, and driving it found two deep, correct JavaScript-semantics fixes that matter far beyond automation: spreading an object now reads its getters (the way bundled modules export everything), and listing an object's property names now includes accessor properties. Both are exactly what the language specifies. An external, industry-standard tool driving the engine's DOM end to end is the honest definition of the DevTools floor being bridged, so DevTools moves 40 to 42, JavaScript language 81 to 82, and the overall moves to 52.

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	page.$eval and element queries work: Puppeteer injects a utility bundle (an esbuild module) and calls into it to resolve selectors; the engine now runs that bundle faithfully and returns real element handles, so querying the DOM through the standard automation protocol returns the right answer. Verified by the probe script in the repo driving unmodified puppeteer-core: connect, newPage, goto, $eval and evaluate all pass.
Rendering	Object spread now invokes enumerable getters and copies their values, per the ES2018 copy-data-properties rules - the way a bundled module namespace (all getters) is spread to export its members. Previously spread copied raw slots and skipped getters, so such modules exported nothing.
DevTools	Object.getOwnPropertyNames now lists accessor (getter/setter) properties by their public names, as the specification requires - accessors are own properties. The esbuild module wrapper copies a namespace by walking these names, so missing them meant the whole module resolved to nothing. Both fixes ship with language regression tests and leave the whole conformance suite unchanged. Research note docs/devtools-target-model-plan.md.