Contact emailspth...@chromium.org, math...@chromium.org Explainerhttps://github.com/tc39/proposal-regexp-v-flag https://v8.dev/features/regexp-v-flag
Specificationhttps://github.com/tc39/proposal-regexp-v-flag Summary Add set operations, string literals, nested classes and unicode properties of strings to regular expression character classes. Set operations and unicode properties of strings allow developers to create regular expressions matching strings with certain unicode characters with ease. E.g. /[\p{Script_Extensions=Greek}&&\p{Letter}]/v matches all greek letters. Blink componentBlink>JavaScript>Regexp <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EJavaScript%3ERegexp> TAG review TAG review statusNot applicable Risks Interoperability and Compatibility Covered by TC39 process: https://github.com/tc39/proposal-regexp-v-flag *Gecko*: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1713657) Assumed positive because this proposal is Stage 3 in TC39. *WebKit*: Positive (https://bugs.webkit.org/show_bug.cgi?id=241593) Assumed positive because this proposal is Stage 3 in TC39. *Web developers*: No signals *Other signals*: Activation The new features are gated behind a new regular expression flag (/v). See https://github.com/tc39/proposal-regexp-v-flag#is-the-new-syntax-backwards-compatible-do-we-need-another-regular-expression-flag 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? Debuggability Uses existing debugging support for regular expressions. No additions required. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?Yes The feature is enabled for all platforms when compiled with internalization support. Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?Covered by test262: https://github.com/tc39/test262/tree/main/test/built-ins/RegExp/unicodeSets/generated Flag name--harmony-regexp-unicode-sets Requires code in //chrome?False Non-OSS dependencies Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function? no Sample links https://v8.dev/features/regexp-v-flag Estimated milestones DevTrial on desktop 110 DevTrial on Android 110 Planned to ship in M112 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). Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5144156542861312 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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKhjTa_NMAR5FF5zkWDa0msVJk3gHA%3DgnzMndyv-_atBNr%3DQnQ%40mail.gmail.com.
