v0.1.2122 Sep 2026·Rendering, JavaScript & JIT, Networking

Pages you render with Floati's own engine appear right away now

When you render a page with Floati's from-scratch engine (the ... menu, Render this page with the engine), it used to wait for ALL of the page's scripts to finish running before it showed you anything - so a heavy, script-laden page could sit on a spinner for several seconds even though the actual article was ready to draw almost immediately. The engine now works the way a normal browser does: it paints the page the instant it is laid out - the headline, the text, the structure appear at once - and then quietly fills in whatever the scripts change a moment later. The result you end up with is exactly the same, it just stops making you wait for it. A page that is genuinely blank until its scripts build it (a web app shell) still waits for those to run, so it never flashes empty. This is the single biggest step toward Floati's own engine being fast enough to render everything you browse by default: the main reason heavy pages were held back was this wait, and it is gone.

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	Rendering a page with Floati's own engine now shows the page as soon as it is laid out, instead of waiting for every script on the page to finish first. On a heavy, script-heavy page - a news site, a long article with lots of embedded widgets - the readable page appears in a moment rather than after a multi-second pause, and anything the scripts change is filled in right after.
Networking	It works by splitting the load into two steps that produce byte-for-byte the same final page: an early paint the instant the page's structure and styles are ready, and a second paint once the scripts have settled, delivered as a quiet update. Nothing you see changes - the page is identical to before - it just arrives in two quick stages instead of one slow one.
JavaScript & JIT	A page that is deliberately empty until its own code builds it (a single-page web app that mounts everything with JavaScript) is detected and left to finish first, so the engine never flashes a blank frame at you before the real content. Server-rendered pages, which already have their content, get the fast early paint.