v0.1.2195 Sep 2026·Rendering, Web APIs & DOM

The scripts that gave up halfway now finish the job

A round of fixes to how Floati runs a page's JavaScript, aimed squarely at the little things that made real sites quietly stop short. Chief among them: when a page does some work, runs a bit of clean-up afterwards, and then carries on, it used to stop dead at the clean-up step and lose everything after it. That is a pattern on almost every modern site - load something, hide the spinner, then show the result - so fixing it quietly unblocks a lot of pages. Alongside it, a low-level building block that many frameworks lean on to call functions now actually works, swapping one piece of the page for another from a script now takes effect, and turning things on and off from code - hiding an element, marking a field required, switching a page to right-to-left - now shows up on screen. And the tool we use to grade ourselves against the reference browser now watches for any script that throws, so a page that looks right but silently errored can no longer pass as correct.

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 that clean up after their work now finish it. The everyday 'do the work, then run some tidy-up, then continue' pattern used to halt at the tidy-up and drop the rest of the page's logic; it now runs the way it does in other browsers, so spinners hide, results appear, and follow-on steps happen.
Web APIs & DOM	More of the web's framework plumbing runs. A low-level way to call a function indirectly, which a great deal of framework and library code is built on, did nothing before and quietly stalled everything that relied on it; it now works, so that code runs as intended.
Rendering	Swapping part of a page from a script now takes effect. Replacing an element's own markup - a routine way to turn a placeholder into finished content - was being ignored and the page never changed; it now updates in place.
Rendering	Turning things on and off from code shows on screen. Hiding or disabling an element, marking a form field required or optional, or switching a page into right-to-left reading from a script used to change nothing visible; those now apply, so scripted state matches what you see.
Rendering	Our own browser-comparison tool now catches silent script errors. It used to grade a page on its picture alone, so a page that looked right but whose scripts had thrown could pass as correct; it now records every uncaught error per site, which keeps future fixes honest.