v0.1.2205 Sep 2026·Rendering, JavaScript & JIT, Web APIs & DOM

Loops, clicks, and the small print of running a page

A second round of making Floati run real pages the way other browsers do. The headline is a classic: a for loop now hands each turn its own copy of the counter, so the everyday pattern of making a little function inside a loop - a click handler per row, a timer per item - remembers the right value instead of every one of them seeing the last. Real clicks now behave like real clicks: they run 'capture' listeners on the way down, report which phase they are in, and identify themselves as genuine rather than script-made, so delegation and click-guards work. Math gained the functions and constants it was missing, the error that Promise.any is meant to hand you - carrying the list of what failed - now exists, and reading an element's parent no longer stops one step short at the top of the page.

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

JavaScript & JIT	Making a function inside a for (let ...) loop now captures that turn's value. Every function made in the loop used to share one counter and see its final value - the most common surprise in JavaScript loops - so a row of buttons wired up in a loop all did the last row's thing. Each turn now gets its own binding, like every other browser. Plain counting loops are untouched and just as fast.
Web APIs & DOM	Real clicks and key presses now run the full event path: 'capture' listeners fire on the way down, the event reports which phase it is in, and it identifies itself as a genuine user action. Code that listens on a container and works out which child was clicked, and guards that only trust real clicks, both work now.
Rendering	Math gained its missing pieces: the inverse hyperbolic functions and every standard constant (root two, the natural logs, and the rest), so maths-heavy and feature-detecting code that reaches for them no longer trips.
JavaScript & JIT	Promise.any now hands your catch block the proper error carrying the list of every reason that failed, instead of a bare message - the whole reason to reach for it. The error type behind it now exists in its own right.
Rendering	Reading an element's parent is correct at the very top of the page now: the generic parent-node keeps walking up to the document, while parent-element stops at the last real element, instead of the two being identical and cutting a walk-up short.