[Webkit-unassigned] [Bug 210309] New: [YARR] Allow for Unicode named capture group identifiers in non-Unicode regular expressions

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=210309

            Bug ID: 210309
           Summary: [YARR] Allow for Unicode named capture group
                    identifiers in non-Unicode regular expressions
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: msaboff at apple.com

During the March/April 2020 TC-39 meeting, it was agreed that named capture group identifiers can contain unicode escape characters even for non-unicode flagged regular expressions.  This change is part of the EcmaScript 2020 draft standard that was approved by TC-39 at the same meeting and should be ratified by the Ecma General Assembly in June 2020.

The current 2019 standard allows the following constructs for named capture group identifiers with non-BMP codepoints
    let regex1a = /(?<��>A)/u;
    let regex1b = /(?<\u{1d49c}>A)/u;
    let regex1c = /(?<\ud835\udc9c>A)/u;
    let regex2a = /(?<��>A)/;  // no u flag 
But didn’t allow non-BMP unicode escapes in named capture group identifiers for non unicode regex’s
    let regex2b = /(?<\u{1d49c}>A)/;
    let regex2c = /(?<\ud835\udc9c>A)/;

JavaScriptCore has a bug where it doesn’t even allow regex2a.

This is to track fixing the JSC bug for regex2a, and adding the two other non-unicode forms to bring JSC into compliance with the 2020 standard.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200409/c5fb88ef/attachment.htm>