W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2012

[whatwg] [JavaScript / Web ECMAScript] Dropping the “escaped reserved words” compatibility requirement

From: Mathias Bynens <mathias@qiwi.be>
Date: Thu, 5 Jul 2012 10:47:46 +0200
Message-ID: <CACrCd9PgiCX73158vRUDdUZZsvY==78pUApmci9=7iaWzV72WA@mail.gmail.com>
To: whatwg@whatwg.org
http://mathias.html5.org/specs/javascript/#escaped-reserved-words says:

> JavaScript implementations must support ECMAScript identifiers that unescape
> to a reserved word, as long as at least one character is escaped using a
> Unicode escape sequence.
>
> For example, var var; throws a syntax error, but e.g. var v\u0061r; works
> fine.
>
> Subsequent use of such identifiers must also have at least one character
> escaped (otherwise the reserved word will be used instead), but it doesn’t
> have to be the same character(s) that were originally used to create the
> identifier.
>
> For example, var v\u0061r = 42; alert(va\u0072); alerts 42.

One year ago, all browsers except IE fulfilled this compatibility requirement.

Half a year ago Firefox dropped this non-standard addition
(https://bugzilla.mozilla.org/show_bug.cgi?id=694360) and hasn’t seen any
compatibility issues since.

Has the time come to drop this compatibility requirement?
Received on Thursday, 5 July 2012 08:48:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:09 GMT