v0.1.3311 Oct 2026·Rendering, Memory & reading

A crash on busy news sites fixed, and pages lighter on the processor

Floati could crash while loading busy pages like a news site homepage, about half the time. The cause was a fast path for calling functions that kept using an old copy of the page's compiled code after that copy had been freed. It is fixed. Pages also take less processor time to load: about 20 percent less for a large encyclopedia, 11 for a news site and 8 for a code-hosting site, with every site we test rendering pixel for pixel the same as 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

Memory & reading	Fixed: a news site homepage, and other pages that load many scripts, could crash while loading. As a page loads more scripts, the engine moves its compiled code to a bigger block of memory. One fast way of calling a function (building the called function's frame directly in machine code) remembered where the code used to be, so after the move it ran instructions out of memory that had already been freed. That call path now looks up the current code every time, as the regular path always did. A news site page went from crashing about half its loads to zero in 18.
Rendering	Style lookups take one step. Layout constantly asks each element for values like its font and colour that it inherits from its parents. Each of those questions used to walk up the page, one step per ancestor that set an inherited style, and even questions about styles that are never inherited made the full walk before answering. Inherited styles are now kept in one table per element, so every answer is a single lookup. This was the largest single cost on a large encyclopedia and a news site.
Rendering	Fixed: el.querySelectorAll(':scope > li') found nothing. The :scope selector means the element you are searching from, and Floati treated it as the whole page, so code that looks for an element's own children (common in libraries such as jQuery and Lit) came back empty. querySelector, querySelectorAll, matches and closest now all give the same answers as the reference browser, checked case by case against it.
Rendering	A selector that can only match one element no longer scans the page. A large encyclopedia asked for ':scope' more than a thousand times while loading, and each request walked every element on the page; Floati now checks the one element such a selector can match. That alone saved about a third of a second on a large encyclopedia.
Rendering	Reading an element's attributes no longer makes a copy of the attribute's name each time.