The hacks I've seen for identifying a JavaScript version are all tailored to the browser, not an ASP Classic server running JavaScript.
(And no, I'm not running ASP Classic/JavaScript by choice.)
The hacks I've seen for identifying a JavaScript version are all tailored to the browser, not an ASP Classic server running JavaScript.
(And no, I'm not running ASP Classic/JavaScript by choice.)
Disclaimer: I'm an engineer on Microsoft's JavaScript team (specifically, Chakra).
The IActiveScript
JavaScript engine used by "Classic ASP" is also used by the Windows Script Host (cscript
and wscript
) and was also used by IE for a while (IE9 and later, certainly does not).
Anyway, the JScript engine generally coincides with the ECMAScript 3.0 specification with some proprietary extensions (such as ActiveXObject
). The specification is available here: http://www.ecma-international.org/publications/files/ECMA-ST-ARCH/ECMA-262,%203rd%20edition,%20December%201999.pdf - this specification was written in 1999.
This version of JScript has not been updated much since the days of Windows 2000 (i.e. no new features have been added, the only changes have been for the benefit of security).
As such, it does not include features introduced in ECMAScript 5, like strict mode, or Array.isArray
.
© 2022 - 2024 — McMap. All rights reserved.
<%@ Language = "JScript" %>
processing directive. Do not confuse JScript with JavaScript there are differences (as @Dai point's out in their answer below). – Hestia<%@ language=JavaScript %>
also works, at least sometimes. It's what the system I'm using starts its ASP files with. – LamebrainJScript
. The scripting engine used is the same. – Hestia