Closed
Bug 592274
Opened 14 years ago
Closed 14 years ago
Implementation status table claims we don't support "use strict"
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 482298
People
(Reporter: jwatt, Unassigned)
References
()
Details
The following webpage claims FF4 beta 5 pre doesn't support "use strict": http://kangax.github.com/es5-compat-table/ See comment at the bottom of the page for how they test.
Reporter | ||
Updated•14 years ago
|
blocking2.0: --- → ?
Comment 1•14 years ago
|
||
Looks like a dup of bug 514570?
Comment 2•14 years ago
|
||
It's really just the bug with alias es5strict -- we aren't done yet, but we will be for Mozilla 2.0 / Firefox 4. /be
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Comment 3•14 years ago
|
||
IOW, that |this| coercion bug is supposed to be the very last bug that anyone implementing ES5 strict on top of an ES5-without-strict implementation should fix, lest that (function () { "use strict"; return !this; })() detection technique give the wrong answer. /be
Comment 4•14 years ago
|
||
It's hard to choose one item from the extensive list of things that strict mode brings to the table. The reason I ended up with this-coercion is because, as Brendan says, it's likely one of the last things to be implemented, making it a better indication of "strict mode support". IIRC, `(function(){"use strict"; return !this})()` was also mentioned by Mark Miller on es-discuss some time ago (as, probably, the "shortest" way to test strict mode support), so that little snippet just "sticked". For a more or less complete list of supported features, the link in that same compat table references this page — http://kangax.github.com/es5-compat-table/strict-mode/ , where Mozilla is, in fact, leading right now. Another option — which I might implement in the future, if I find time — is to perform all of the "strict mode" tests and write percentage, rather than somewhat unfair yes/no.
Updated•14 years ago
|
blocking2.0: ? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•