Contact emails...@chromium.org Explainerhttps://github.com/tc39/proposal-is-usv-string/blob/main/README.md
Specificationhttps://tc39.es/proposal-is-usv-string Summary Add two String.prototype methods for working with well-formed UTF-16 strings. A JavaScript string value is well-formed UTF-16 if it has no unpaired surrogate code points. By default, JavaScript strings may be ill-formed. - String.prototype.isWellFormed returns whether the receiver string is well-formed UTF-16. - String.prototype.toWellFormed returns a string that is identical to the receiver string, except all unpaired surrogate code points are replaced with U+FFFD (REPLACEMENT CHARACTER). Blink componentBlink>JavaScript>Language <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EJavaScript%3ELanguage> TAG review TAG review statusNot applicable Risks Interoperability and Compatibility No known compatibility risk. Though all additions to built-in prototypes such as String.prototype carry non-zero risk in light of polyfill libraries. No interoperability risk. This is a Stage 3 TC39 proposal. *Gecko*: In development ( https://bugzilla.mozilla.org/show_bug.cgi?id=1803523) *WebKit*: In development (https://bugs.webkit.org/show_bug.cgi?id=248588) *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? Debuggability Debuggable like other built-in String methods. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?Yes Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?In test262 <https://github.com/tc39/test262/pull/3661> Flag name--harmony-string-is-well-formed Requires code in //chrome?False Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=13557 Estimated milestones DevTrial on desktop 111 DevTrial on Android 111 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/5200195346759680 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/CAN-e9e_CJVsBrz%2Bc-Ujb-XEEi4GOjayd1cR77v9EMs5RoCNW_g%40mail.gmail.com.