v0.1.6030 Jul 2026·Rendering, Networking, Accessibility, DevTools

Text that measures like the reference browser, an accessibility tree, web security, and animations

The biggest release so far: six things the engine simply did not have, plus eleven rendering fixes, every one checked pixel for pixel against the reference browser. The largest is text. On a Mac the system typeface is a variable font, and a browser is meant to pick a different cut of it at every size. We were using one fixed cut for everything, which made text up to 11 percent too narrow at small sizes and threw off where every line broke. The engine now bakes the right cut per size and applies the tracking macOS adds on top, so the width of a line of text is within about one percent of the reference browser from 12 pixels up to 64. Second, an accessibility tree: the engine can now describe a page the way a screen reader sees it, with roles, names, states, live announcements, tab order and the position of everything, plus a built-in audit that flags a button with no label or a heading level that skips. Third, web security that was simply missing: a page's Content Security Policy is now obeyed, so a script the site asked to block really is blocked, along with cross-origin rules, cookie same-site protection and referrer trimming. Fourth, CSS animations. Without them a page that fades its content in was not just missing the motion, it was stuck on the wrong frame and could render blank. Fifth, a developer inspector for the engine's own boxes and styles. And underneath it all, a fundamental piece of page layout that was missing entirely: the way a wrapper and its first child share a margin, which affects the vertical rhythm of nearly every page on the web.

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 11 changes

Rendering	Text on a Mac now uses the right cut of the system typeface for each size, plus the tracking macOS applies, so line widths land within about one percent of the reference browser from 12 to 64 pixels, where they were up to 11 percent too narrow.
Accessibility	Accessibility: the engine builds the tree a screen reader reads, with roles, names, descriptions, states, live announcements, keyboard tab order and on-screen positions, and can audit a page for unlabelled controls, empty headings and skipped heading levels.
Networking	Security: a page's Content Security Policy is now enforced, so a script it asked to block is blocked. Cross-origin request rules, cookie same-site protection with the secure-prefix rules, referrer trimming and mixed-content blocking all work too.
Rendering	CSS animations run: keyframes, easing curves including steps and custom curves, delays, repeats, directions and fill modes, with colours, lengths and transforms blending properly. A page that fades its content in no longer renders blank.
Rendering	A wrapper and its first child now share a margin the way the standard requires. This was missing entirely and it affects the vertical spacing of almost every page.
Rendering	A see-through border on a rounded box is drawn as a ring instead of a filled shape underneath the background, which fixes frosted-glass panels reading as washed-out white.
Rendering	Text sits centred in its line rather than jammed to the top, so any page that sets a generous line height no longer draws its text a quarter of a line too high.
Rendering	Boxes that count their border and padding inside their width now shrink correctly in a flexible row instead of overflowing off the edge.
Rendering	Margins on inline images and controls are honoured, where before they were dropped entirely.
Rendering	Checkboxes, radio buttons, progress bars and meters are drawn the way the reference browser draws them, including the disabled state, and form control text sits on the same line as the reference browser puts it.
DevTools	A developer inspector: ask the engine for its box tree with geometry, or for one element's boxes and full computed style.