v0.1.1717 Jul 2026·Rendering, Media, Privacy & Shields, Tabs & interface

Engine pages become real tabs

Pages rendered by Floati's own engine now fill the tab like any other page: real size, native scrolling, clickable links, typing. Behind it is viewport-windowed rendering -> the engine paints only what you can see and repaints as you scroll -> so very long pages (a full encyclopedia article) display end to end where they previously could not. A new Developer mode in Settings houses the engine playground. Plus the app never freezes during an engine render anymore, and a batch of engine fixes: multi-glyph SVG logos, image-heavy CDNs, CSS math functions, and two deep JavaScript correctness fixes.

Parity with the reference browser

74overall, as of v0.1.355

Web APIs / DOM surface53

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

Tabs & interface	Full-tab engine rendering: a page on Floati's engine fills the tab -> native scroll, links click through, fields type, the address bar shows the real URL. The cramped preview box is gone.
Tabs & interface	Viewport-windowed painting: the engine renders just the band around what you see and repaints on scroll, so 20000px-long articles display end to end. Scrolling costs one band paint -> layout and styling are cached until the page actually changes.
Media	The app stays fully responsive during engine renders (they used to block the interface), and pages with long embedded videos no longer stall loads for minutes.
Privacy & Shields	Developer mode in Settings: the engine playground (live HTML/CSS/JavaScript against the engine) now lives behind a toggle, off by default.
Rendering	Engine correctness: multi-glyph SVG wordmarks render (the encyclopedia's logo), hotlink-protected CDNs serve real thumbnails (old.reddit), CSS min()/max()/clamp() evaluate, arrow functions capture this correctly and class statics inherit -> the two fixes behind a whole class of modern-bundle failures.
Rendering	A layout runaway that could crash the app on grid-heavy sites (example.org) is fixed, tagged template literals run (styled-components sites), and narrow-column squish on Q&A-site layouts is gone.