Floati Browser / Release notes

v0.1.0 - 0.1.9 · 10-12 Jul 2026334 releasesv0.1.343 · 6 Oct 2026

108 built 53 underway 144 still on the roadmap 0 lit by this release

0The engine exists

1Reading-grade rendering

2App-grade JavaScript & web APIs

3Media

4Graphics, compositing & the GPU

5Security & multi-process

6The rest of the web platform

7Accessibility, tooling & polish

★The reference browser parity, on our own engine

Hover or drag along the releases above to see the engine at that moment. Each feature lights up in the release that started it and the release that finished it; recent releases also light every feature they worked on.

Browse releases by topic

v0.1.18919 Aug 2026·Rendering, JavaScript & JIT, Tabs & interface

The encyclopedia's appearance controls and side menus work again

On a large encyclopedia and other wiki sites, the panel that changes the text size, page width and colour theme did nothing when you clicked it, and the collapsible side menus would not open. Both work now. The cause was deep in how the engine let page scripts step through a group of elements, and fixing it lets those controls start up the way they do in every other browser.

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

Tabs & interface	The appearance controls on a large encyclopedia (text size, page width, colour theme) and its collapsible side menus now respond again, instead of silently doing nothing when clicked.
JavaScript & JIT	A very common way page scripts loop through a list of elements now behaves the way other browsers do, so scripts that relied on it start up fully instead of stopping partway and leaving parts of the page inert.
Rendering	Pages that already worked are untouched; this only unblocks scripts that were getting stuck on that one pattern.