v0.1.4622 Jul 2026·Rendering, Accessibility, Tabs & interface

Pages sit where they should on the screen

This one came from putting Floati next to the reference browser on ordinary reading sites and, whenever something looked off, asking both browsers where they had actually put the box. Six faults turned up, all of them in the plumbing that decides how wide something is and where it goes. The clearest example: A Linux news site was drawing its entire article column off the left edge of the window, with the text cut in half, because the site asks for a negative amount of inner spacing and every browser is supposed to treat that as none. There were five more like it, each small on its own and each capable of wrecking a page. Every fix was checked by rendering the same markup in the reference browser and comparing the result down to the pixel before it was allowed in.

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

Tabs & interface	Article text stays on the screen. A site asking for a negative amount of inner spacing had it applied literally, which pushed a whole page sideways out of the window.
Rendering	Side columns keep their minimum width. A column told never to grow but never to fall below a set width was collapsing to a single pixel and shoving the article off the page.
Rendering	When one part of a row refuses to get any wider, the space it turns down now goes to the parts beside it instead of being left empty.
Rendering	Text inside a box that sits in a line of other content now wraps at the edge of the space it has, instead of running out on one long line past the side of the page.
Rendering	A box asked to fill the width available to it does so, and does it once. It was being ignored outright, and then, once honoured, counted twice, so half-width came out quarter-width.
Tabs & interface	Navigation menus stack one item per line again. Menu links were shrinking to fit their own words and crowding onto shared rows, on a programming-language site, on its documentation, and on a Linux news site.
Accessibility	Wording that a site includes only for screen readers is no longer printed on the page. Every external link on a developer-docs site had the word "(external)" typed into the middle of the sentence around it.