v0.1.26210 Sep 2026·Rendering, Web APIs & DOM, DevTools

Function names, and the standard hooks regular expressions rely on

Three correctness fixes that close gaps against the JavaScript standard real code depends on. Functions defined as methods, getters, setters and class members now report their proper name, the name a debugger, an error trace or a component tool shows, instead of a blank; a great deal of real code reads this to label and dispatch things. The regular-expression objects built into the language gained the standard hooks that text search, match, split and replace rely on, so more library and framework code that leans on regular expressions now works unchanged where before it hit a missing-function error. And building a regular expression with an invalid or repeated set of option letters is now rejected up front, the way every other browser does it, rather than quietly producing a broken one. None of this changes code that was already correct. The JavaScript language aspect moves 88 to 89; 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

DevTools	Functions report their real name. A method, getter, setter or class member defined without its own name now takes the name the standard assigns from where it is defined, so debuggers, error messages and any code that reads a function's name to label or route work correctly instead of seeing a blank.
Web APIs & DOM	Regular expressions gained their standard text-processing hooks. The built-in regular-expression objects now expose the internal methods that the language's own text search, match, split and replace operations call, so library and framework code that reaches for them directly works instead of failing with a missing-function error.
Rendering	Invalid regular-expression options are rejected up front. Creating a regular expression with an unknown or repeated option letter, or an incompatible pair, now reports the error immediately as other browsers do, rather than silently building one that behaves wrongly later.