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.18619 Aug 2026·Rendering, Memory & reading, Tabs & interface

Engine tabs remember where you were

A small follow-up to yesterday's update. When you switched away from a tab rendered with Floati's own engine and came back, the page jumped back to the top instead of staying where you had scrolled to. Now it returns you to exactly where you left off, the way every other tab does.

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	Switching away from an engine-rendered tab and back now returns you to the spot you had scrolled to, instead of jumping back to the top of the page.
Tabs & interface	Links you hover stay responsive right after switching tabs, since the page no longer rebuilds its position from scratch.
Rendering	This rounds off yesterday's update that made engine-rendered pages behave like real pages.