v0.1.4321 Jul 2026·Rendering, Web APIs & DOM

The heavy pages get another three to six times faster

The speed work continued straight after the morning release, and the profiles kept naming real problems. The biggest was hiding in tables: to size a table the engine measured every cell once, then laid every cell out a second time at its final position. Tables inside tables therefore doubled the work at every level of nesting, and one box on an encyclopedia article was being laid out 4,096 times. The cell is now simply moved to its final position instead of being rebuilt, and that article's layout went from about a second to 82 milliseconds. Style matching got sharper too: utility-style class names with escaped characters, which modern design systems use heavily, were being tested against every element on the page instead of being looked up like normal classes - on a Q&A site question that alone removed almost two seconds. As always, every page was verified to render pixel-for-pixel identically to before.

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	Styling and layout of an encyclopedia article now take 184 milliseconds, from 3.8 seconds at the start of the day - about 21 times faster. A Q&A site question went from 4.3 seconds to 0.45.
Rendering	Tables inside tables no longer multiply layout work: a measured cell is moved to its final position instead of laid out again. One a large encyclopedia box went from being laid out 4,096 times to once.
Rendering	Escaped utility class names (the ones modern design systems generate) are now indexed like any other class instead of being tested against every element on the page.
Web APIs & DOM	Each element's classes are read and split once instead of on every rule test, and every style rule is parsed once when the stylesheet loads instead of on every match attempt.
Rendering	Flexible column layouts measure each item's natural height once instead of rebuilding it for every measurement, with a built-in self-check that verifies the reused answer is exactly what a fresh measurement would give.