Floati Browser / Release notes

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

98 built 40 underway 167 still on the roadmap 1 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.976 Aug 2026·Rendering, Media, Tabs & interface

Real captions

Video and audio elements can now carry real captions. The engine parses WebVTT (the standard caption format) into timed cues with start and end times and text, and exposes them through the standard TextTrack and VTTCue objects a page scripts against, plus addTextTrack and the textTracks list on media elements. That is the path accessible, captioned media takes. Video pixels themselves are still a separate, larger effort, so the Media figure moves for the caption capability, not for decode.

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

Rendering	Added a real WebVTT parser: caption files parse into timed cues (start time, end time, text), the same format the whole web ships captions in, verified against real cue lists including timestamp edge cases.
Media	Exposed the standard captions API: TextTrack and VTTCue objects, WebVTT.parse, and addTextTrack / textTracks on video and audio elements, so page code that builds or reads captions works against the real interface.
Tabs & interface	Captions are an accessibility feature first: timed text tracks are how deaf and hard-of-hearing users, and anyone in a quiet room, follow media, and the engine now models them as real objects rather than ignoring the track.