v0.1.3321 Oct 2026·Rendering, JavaScript & JIT, Web APIs & DOM, Privacy & Shields, Tabs & interface
Pinned tabs on the left or the right, and an honest measure of the web platform
You can now choose where pinned tabs sit: at the left of the tab strip as before, or at the right end, where they stay in view however many tabs are open. Vertical tabs can dock on either side of the window, and new tabs can open next to the tab you are on. Behind the scenes we built three new instruments that compare Floati's web platform with the reference browser's, interface by interface, test by test and site by site, and they replace a judged score with a measured one.
Pinned tabs, left or right. Settings > Appearance has a new Pinned tabs switch. On the right, pinned sites sit together at the right end of the strip, outside the part that scrolls, so they never scroll away when you have dozens of tabs open.
Tabs & interface
Everything follows the screen. Ctrl+Tab steps through tabs left to right, Cmd or Ctrl+1 is always the leftmost tab and 9 the rightmost, and dragging a tab onto the pinned group drops it right beside the group, whichever side it is on.
Tabs & interface
Vertical tabs on either side. The tab sidebar can dock on the right of the window, and pages move over to match.
Tabs & interface
New tabs next to the one you are on. A new tab from the + button or the new tab shortcut can open right after the current tab instead of at the end; links and menus keep their own placement.
Tabs & interface
Fixed: New tab to the right and Duplicate tab on a pinned tab put an ordinary tab in between your pinned ones. New tabs now always land just outside the pinned group, and the menu says New tab to the left when pinned tabs sit on the right.
JavaScript & JIT
A whole-platform census. A new tool lists every interface the reference browser exposes (917 of them, with 7,554 members, not counting JavaScript's own built-ins) and checks each one in Floati for its exact shape: the same kind of property, the same flags, the same place in the inheritance chain. Run inside the reference browser itself it scores 100 percent, so the tool is proven before it judges us. Floati scores 0.8 percent: most pages work because the engine answers on live elements, but frameworks and feature checks look for the exact shape, and that is what is missing.
Web APIs & DOM
The official tests, scored against the reference browser. Floati now runs the web-platform-tests for the DOM (the shared conformance suite every browser maker uses) and counts only the 59,635 checks the reference browser itself passes. Floati passes 3.8 percent today, and the tool names the cause first: 49,513 of the misses come from one missing piece (creating XML documents), which a shared test setup needs before the rest can even run.
Rendering
Script errors on real sites. Twelve live sites are loaded in Floati and in the reference browser, and a site passes only if Floati throws no script error the reference browser does not. Four of twelve pass today, and each failure names a concrete fix, such as a missing timeRemaining on idle callbacks (a large encyclopedia) and symbols used as weak map keys (a news site).
Privacy & Shields
An honest score. The Web APIs and DOM row was a judged 80, set when we counted 577 hand-picked names. It is now the lowest of the three measured checks, so it reads 1, and the overall moves from 77 to 73. The plan to 100 is to generate every binding from the web standards' own interface definitions, the way the reference browser does, and then go further where the reference browser stops: faster DOM calls that compile straight into machine code, a radar that shows which page fingerprinted you, location shared at city level instead of to the metre, and pages you can record and replay exactly.