v0.1.28411 Sep 2026·Rendering, Tabs & interface

Pop-out menus size to their contents, and pages get complete answers about their own styling

Two rendering-correctness fixes, both on your device. When a site opens a drop-down or a pop-out panel that is meant to be as wide as whatever is inside it, the browser now lets it grow to fit its contents instead of squashing it into the narrow strip it hangs off, so wide navigation menus and mega-menus open at their real width the way they do elsewhere. And when a page asks the browser to report the final, computed look of an element - the everyday way a page checks whether something is visible, how it is arranged, or what a colour turned out to be - every property now comes back with a real value rather than a blank, so pages that adapt themselves to their own measurements behave correctly. The Web APIs and interface-surface aspect moves 71 to 72; 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 3 changes

Tabs & interface	A pop-out menu or panel that is meant to hug its contents no longer collapses to the width of the button it hangs off. An overlay told to be as wide as its content is now allowed to run past the small box it is anchored to, which is how every other browser draws it, so a site's mega-menu opens at full width instead of a squashed sliver. The two related content-sizing modes - as-wide-as-possible-content and as-narrow-as-possible-content - are now handled distinctly and correctly too.
Rendering	When a page asks for an element's fully computed styling, every property now answers with a real value. Previously around fifty layout and appearance properties came back blank unless the page had set them by hand, which quietly broke the very common helper code that asks whether something is visible, whether it is laid out as a row or a column, or what colour it ended up. Each value was checked against a mainstream browser across many thousands of real page elements to make sure it matches.
Rendering	The old and new spellings of the rule that lets a long word break rather than overflow now agree. A page that reads back either spelling sees the one value they both stand for, matching other browsers, so text-wrapping code that feature-detects the setting no longer gets a misleading answer.