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

WebAssembly now rejects broken modules, as a browser must

A real browser type-checks every WebAssembly module before running it and refuses the broken ones: a module that adds a whole number to a decimal, jumps to a code label that does not exist, or names a function or variable that was never declared is a compile error, not something you run and hope for the best. Floati's engine had been skipping that check - it would decode almost anything and execute it, which is both a correctness problem (a wrong answer instead of a clear error) and a safety one (untrusted code should be validated, not trusted). This release adds the full validation pass and now rejects every one of the specification suite's 727 hand-crafted invalid and malformed modules, while still running all 13,188 of the valid ones exactly as before. WebAssembly in Floati is now complete end to end for its core and reference-types feature set - it decodes, validates, and executes to the letter of the spec - which brings the scorecard to 63.

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

JavaScript & JIT	Invalid WebAssembly is now refused, not run. The engine performs the standard validation pass - tracking the type of every value on the stack through every branch and loop - and rejects a module whose types do not line up, that branches to a label that is not there, or that references a function, local, global, table or type that was never declared. Previously such a module was decoded and executed anyway, producing a wrong result instead of the compile error a browser is required to give.
Web APIs & DOM	Malformed modules are caught at the door. A global with an out-of-range mutability flag, a table declared with a non-reference element type, or a constant initializer that reads a variable not yet in scope are all now rejected during decoding, matching the reference implementation.
Rendering	Proven both ways against the official suite. All 727 of the specification's hand-written invalid and malformed test modules are now correctly rejected (up from a handful), and - just as important - all 13,188 valid behavioural checks still pass unchanged, so nothing that should run was broken by the new strictness. A permanent gate locks both numbers in.