Chakra: Use Unicode 6.1.0 when determining whether an identifier is acceptable or not - by MathiasBynens

Status : 

  Postponed<br /><br />
		Due to current priorities, the product team decided to postpone the resolution of this item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

ID 725622 Comments
Status Resolved Workarounds
Type Bug Repros 2
Opened 2/19/2012 8:40:25 AM
Access Restriction Public


Chakra currently uses an older version of the Unicode database. Here are some examples of identifiers that are currently failing because of this, even though they’re valid according to ES 5.1/Unicode 6.1:

* `var \u0cf1;` —
* `var \ua7aa;` —
* `var \u1bba;` —
* `var a\ua674;` —

Of course, there are many more. See

Updating to Unicode 6.1 would improve interoperability.
Sign in to post a comment.
Posted by Microsoft on 7/9/2013 at 1:01 PM
Thank you again for your feedback.

We were able to validate your feedback. However, based on the limited impact this bug may have, we will not be able to address this bug during this release.

Your feedback is very important to us, and it helps us improve the quality of Internet Explorer. We continue to welcome more feedback, so please don't hesitate to report other ways that we can improve Internet Explorer.

Best regards,
The Internet Explorer Team
Posted by MathiasBynens on 6/2/2012 at 2:45 AM
Test case with 90k+ assertions:
Posted by MathiasBynens on 2/20/2012 at 1:01 PM
Why was this bug closed as “not reproducible”? It clearly is.

Here’s the test page:

Here’s a screenshot:

As mentioned before, the simplest way to reproduce the issue is to just open up the F12 developer tools and enter this in the JavaScript console:

    var \u0cf1;