v0.1.4522 Jul 2026·Rendering, JavaScript & JIT, Tabs & interface

The websites that used to come out broken now come out right

This is the biggest correctness release so far. Almost every large website ships one small starter script whose only job is to pull in the rest of the code; Floati was running the starter and then stopping, so the real code of those sites never arrived. Fixing that opened the door to everything behind it, and behind it were fifteen genuine faults in how Floati understood JavaScript and positioned things on the page. Each one was found the same way: load a real website, ask it what went wrong, fix the cause rather than the symptom. Sites built on the widget libraries that a large part of the web still uses were locking up. Pages that write their styles inside their code, which is how most modern sites are built, were failing to load their appearance at all. Search boxes were drawing their magnifying glass clipped off the top. Menus that are supposed to sit off screen were painting straight over the page. All of that is fixed, and the everyday result is simple: pages that used to come out wrong now come out right.

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

Rendering	Sites that load their code in pieces now load all of it. A large encyclopedia downloads and runs its real software, the same as in the reference browser, instead of stopping after the starter script.
JavaScript & JIT	Websites built with the widget libraries that much of the web still runs on no longer lock up. A single fault made every widget on a page share one identity, which sent those sites into an endless loop until they gave up.
Rendering	Pages that keep their styling inside their code now show it. Floati was only reading styles written directly in the page, so anything a modern site built at runtime came out unstyled.
Rendering	Search boxes look right. The magnifying glass inside a search field was drawn clipped off the top edge on a large encyclopedia, and floating outside the box entirely on other sites.
Tabs & interface	Slide-out menus stay hidden. Navigation panels that are meant to sit off the side of the screen were being painted over the middle of the page, hiding the content behind them.
JavaScript & JIT	Several very common pieces of JavaScript punctuation were being misread, and a single misread would silently discard an entire file. Sites whose styling is written inside their code, which includes some of the largest news sites, were losing whole files this way.
Rendering	Text no longer drifts away from the box it belongs to when a page moves something across the screen.
Rendering	Dates can be changed, not only read. Anything that sets a reminder, an expiry or a countdown works now; a site preference that would not stick was traced to exactly this.
Tabs & interface	A large amount of everyday browser vocabulary that pages expect was missing and is now present, including the full drop-down menu controls, the modern ways of adding content to a page, and reading a page address apart.
Rendering	Error messages now name what actually failed. Before, a problem in a compressed site file reported a name that appeared dozens of times in it, which made a real cause impossible to find.