*> Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?* *> No*
Should this be "yes" or is there a reason we'd roll this out only on certain platforms? *> Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?> No* I assume this has test262 coverage, though -- is that right? On Monday, November 9, 2026 at 5:40:43 AM UTC-8 Chromestatus wrote: > *Contact emails* > [email protected], [email protected] > > *Explainer* > https://github.com/tc39/proposal-regexp-buffer-boundaries > > *Specification* > https://tc39.es/proposal-regexp-buffer-boundaries > > *Summary* > A TC39 proposal introducing `\A`, `\z` and `\Z` character escapes to > Unicode-mode regular expressions as synonyms for `(?-m:^)`, `(?-m:$)` and > `(?=(?:\r\n|\n|\r|\u2028|\u2029)?(?-m:$))`, respectively. > > *Blink component* > Blink>JavaScript>Regexp > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EJavaScript%3ERegexp%22> > > *Web Feature ID* > Missing feature > > *Motivation* > *No information provided* > > *Initial public proposal* > *No information provided* > > *TAG review* > *No information provided* > > *TAG review status* > Not applicable > > *Goals for experimentation* > None > > *Risks* > > > *Interoperability and Compatibility* > *No information provided* > > *Gecko*: Shipped/Shipping ( > https://www.firefox.com/en-US/firefox/155.0a1/releasenotes) > > *WebKit*: No signal > > *Web developers*: No signals > > *Other signals*: > > *WebView application risks* > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > *No information provided* > > > *Debuggability* > *No information provided* > > *Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, ChromeOS, Android, and Android WebView)?* > No > > *Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* > No > > > *Flag name on about://flags* > *No information provided* > > *Finch feature name* > V8Flag_js_regexp_buffer_boundaries > > *Rollout plan* > Will ship enabled for all users > > *Requires code in //chrome?* > False > > *Tracking bug* > https://g-issues.chromium.org/issues/517575874 > > *Estimated milestones* > Shipping on desktop 159 > Shipping on Android 159 > Shipping on WebView 159 > > *Anticipated spec changes* > > Open questions about a feature may be a source of future web compat or > interop issues. Please list open issues (e.g. links to known github issues > in the project for the feature specification) whose resolution may > introduce web compat/interop risk (e.g., changing to naming or structure of > the API in a non-backward-compatible way). > *No information provided* > > *Link to entry on the Chrome Platform Status* > https://chromestatus.com/feature/5187917373898752?gate=6115713719861248 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com>. > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/1e6a78b4-0859-4fd9-bedb-be6eeb3bdd08n%40chromium.org.
