Bug 6179 – We treat "char" as a reserved word in JavaScript and firefox/IE do not

• Status: RESOLVED
• Resolution: FIXED
• Component: JavaScriptCore

[Eric Seidel (no email)]

We treat "class" as a reserved word in JavaScript and firefox does not

[Eric Seidel (no email)]

Created attachment 5200 [details]
testcase

[Eric Seidel (no email)]

This looks to be a bug in FireFox, not in Safari.  Filed as:
https://bugzilla.mozilla.org/show_bug.cgi?id=321079

[Eric Seidel (no email)]

Actually, let's reopen this, as there are several reserved words which both IE and firefox allow, yet we do 
not.

FireFox has a bug which they originally fixed for this:
https://bugzilla.mozilla.org/show_bug.cgi?id=240317

And a test case:
https://bugzilla.mozilla.org/attachment.cgi?id=206492&action=view

As part of the bug which I filed their they are looking to update their behavior to better match IE, which 
we should also consider:
https://bugzilla.mozilla.org/show_bug.cgi?id=321079

[Maks Orlovich]

KDE bug #120925 (http://bugs.kde.org/show_bug.cgi?id=120925) is basically about this; it affects http://www.orange.co.il/catalog/

The keywords there are "goto" and "package"

[Francisco Tolmasky]

I don't know about char, but I believe class is supposed to be reserved for "later use".

[Geoffrey Garen]

FF reserves no "future reserved words" and the Mozilla Bugzilla entry suggests they don't plan on changing.

IE reserves the following "future reserved words": class, enum, extends, super, export, import.

[Geoffrey Garen]

Created attachment 8339 [details]
Fix

Posting patch for posterity -- Maciej already reviewed it.

[Geoffrey Garen]

Landed as r14403.

[Alexey Proskuryakov]

*** Bug 12527 has been marked as a duplicate of this bug. ***