v0.1.30824 Sep 2026·Rendering, Web APIs & DOM, Memory & reading, Tabs & interface

Pages drawn by your graphics card, and scrolling that never waits

This release moves the engine's drawing onto your graphics card. Every page the engine renders is now painted by the GPU (Metal on macOS, DirectX 12 on Windows), and the result is proven identical, pixel for pixel, to the careful software painter it replaces: across the whole test corpus not a single pixel differs. The pixels also never make a round trip back to the processor; they are drawn straight into the graphics memory the window shows. Scrolling now works the way the reference browser's does. A separate compositor thread holds a snapshot of the page and serves every scroll from it, so a scroll never waits for the page's own scripts or layout. It goes one step further than the reference browser: while you pause, it paints ahead in the direction you were heading, further the faster you scroll, so the next scroll usually lands on rows that are already drawn. A scroll now takes one to two milliseconds on macOS and under ten on Windows. Alongside that come fixes you can see: radio buttons draw and click correctly, the bottom of long encyclopedia articles (references and footer) is back, pages stay sharp at 125 and 150 percent display scaling, and an idle page no longer keeps the processor busy.

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

Rendering	Pages are painted by your graphics card, and the result is identical to the software painter, pixel for pixel, on every page we test. Only the rare effects the GPU path does not model yet (blend modes, backdrop blur) quietly fall back, a row at a time.
Rendering	Scrolling never waits on the page. A dedicated compositor thread serves each scroll from a snapshot of the page, and while you pause it paints ahead in the direction you were scrolling, so scrolling a long article stays full and fast instead of flashing blank.
Tabs & interface	GPU drawing is on by default on Windows as well (DirectX 12), and it recovers on its own if the graphics driver resets. Pages also render at your display's true scaling, so text stays crisp at 125 and 150 percent.
Memory & reading	Only what changed gets redrawn. Each strip of the page is remembered by its content, so hovering a link repaints one strip and an unchanged page costs the graphics card nothing. An idle page with a hidden animation dropped from a whole processor core to almost nothing.
Web APIs & DOM	Fixes you can see: radio buttons and checkbox-style controls draw in the right place and respond to clicks (including clicking their label); long encyclopedia articles show their references and footer again instead of a blank tail; drop shadows are no longer cut off at the edge of a scroll.