v0.1.28211 Sep 2026·Rendering, Privacy & Shields

One tracker can't follow you between the sites it sits on, and insecure content shown and healed

A deeper round of protection you can see, all decided and kept on your device. A company that embeds itself inside the pages you visit - the little widgets, the login boxes, the ad slots - is now sealed into its own compartment on each site, so what it stores while riding one site cannot be read while it rides another, and a page can only reach into a piece it embedded when that piece belongs to the same site, never across the boundary. The browser also shows its secure-connection work for the first time: when part of a secure page was requested over an insecure link, you can see what was quietly loaded over a secure connection instead, and for the riskier parts that had to be refused there is now a one-tap way to try loading them securely. And the shield marks itself when it turns something away, so you notice without going looking. The security architecture aspect moves 61 to 64; the overall platform score stays at 70.

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

Privacy & Shields	A tracker embedded on many sites can no longer join them up. Anything a third party embedded inside a page keeps in its own sealed compartment for the site you are actually on, so the same widget riding two different sites cannot recognise you as the same person across them. Your own sites keep working exactly as before.
Rendering	A page can only read into what genuinely belongs to it. Content one page embeds from another place is reachable from that page only when the two are the same site; across a site boundary it stays closed off, the rule that stops one site from quietly reading another's embedded content.
Rendering	See the secure-connection work, and heal what was refused. When a secure page asked for part of itself over an insecure link, the panel now shows what Floati quietly loaded over a secure connection instead. For the riskier active parts that had to be refused outright, a single tap tries loading them over a secure connection, so the page can come back whole without anything ever travelling in the clear.
Privacy & Shields	The shield tells you when it stopped something. If active content on a secure page was refused for being insecure, the shield marks itself so you notice there is something worth a look and an action waiting, rather than only finding out if you happen to open the panel.