v0.1.26710 Sep 2026·Rendering, Web APIs & DOM

Global feature detection and function introspection match the standard

More of the language's introspection brought in line with the standard. Many web apps decide whether a capability is available by asking whether the page's global object has it by name. A function defined at the top level now shows up correctly in that check, so libraries that install and then detect themselves this way work instead of taking a broken fallback path. Listing what a page has defined at the top level now includes those functions too. And inspecting a single function's own details, its name, how many arguments it declares, and its blueprint object, now matches what every other browser reports, so tooling and frameworks that read this succeed. Code that was already correct is unchanged. The JavaScript language aspect moves 93 to 94; 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

Rendering	Detecting a capability on the page's global object works. When code asks whether the global object has a given name, a function declared at the top level now answers yes, as the standard requires. Libraries and polyfills that install themselves globally and then feature-detect by ownership now find themselves instead of falling back to a slower or broken path.
Rendering	Listing what is defined globally includes top-level functions. Enumerating the names the page has defined at the top level now includes function declarations, so code that walks the global object sees the full picture.
Web APIs & DOM	Inspecting a function's own details matches other browsers. Reading a function's own properties now reports its name, the number of arguments it declares, and its blueprint object in the standard order, where before that inspection came back empty. Frameworks and developer tools that introspect functions now get the answer they expect.