ES2016 use Unicode 8.0.0 and remove an additional category.
- <p>ECMAScript implementations must recognize as |WhiteSpace| code points listed in the “Separator, space” (Zs) category by Unicode 5.1. ECMAScript implementations may also recognize as |WhiteSpace| additional category Zs code points from subsequent editions of the Unicode Standard.</p>
+ <p>ECMAScript implementations must recognize as |WhiteSpace| code points listed in the “Separator, space” (Zs) category.</p>
It means that ES2016 make U+180E out of whitepace.
eval("1\u180E===1"); // throw exception in ES2016
// SyntaxError: illegal character in ES2016
// `true` in ES2015
This change has included in ES2016 Draft 2016-02-15.
Related items
@BrendanEich @jasvir @awbjs @fugueish @unicode @bterlson So why Chrome/Firefox/nodeJS all eval("1 === \u180E 1") true when specs say no?
— UniqueOde⁰Consortium (@FakeUnicode) March 27, 2016
🤔
@FakeUnicode recent Unicode spec change
— Allen Wirfs-Brock (@awbjs) March 27, 2016
Note all browser updated yethttps://t.co/6h3KwqRvon
@mathiasbynens’s regexpu library already followed this change.
blog comments powered by Disqus
