[Webkit-unassigned] [Bug 4920] Non-BMP characters in JavaScript identifiers

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jun 13 22:22:00 PDT 2011


Gavin Barraclough <barraclough at apple.com> changed:

           What    |Removed                     |Added
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |INVALID
                 CC|                            |barraclough at apple.com

--- Comment #12 from Gavin Barraclough <barraclough at apple.com>  2011-06-13 22:22:00 PST ---
(In reply to comment #11)
> V8 doesn't pass the test case either.  Are we sure this is still a valid bug?

I don't believe this bug is valid.

Section 6 of ES5 defines the meaning of 'character' and 'Unicode character' within the spec.  'Character' refers to precisely one 16-bit UTF-16 Code Unit.  Only the exact phrase 'Unicode character' should refer to a unicode encoded character, possibly represented by a surrogate pair in UTF-16.

Section 7.6 defines the set of characters permissible in Identifiers in terms of the categories of 'characters', i.e. 16-bit Code Units.  Considered individually (as the designation 'character' requires) the two halves of an abstract character formed by a surrogate pair are of code point category Cs, while is not a permissible code point category for inclusion within an identifier.

As such, 𐐀 is not a valid identifier per the ES5 spec.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list