Closed Bug 529206 Opened 16 years ago Closed 8 years ago

v2smap doesn't map "1.85" to JSVERSION_ECMA_5, but JSVersion does

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED DUPLICATE of bug 867609

People

(Reporter: Unfocused, Unassigned)

Details

185 is a valid value for JSVersion, mapping to JSVERSION_ECMA_5. However, v2smap (in jsapi.cpp) maps JSVERSION_ECMA_5 to "ECMAv5". It should also map JSVERSION_ECMA_5 to "1.85", so that consumers (such as nsXPCComponents_Utils::EvalInSandbox) trying to map "1.85" to JSVersion's don't break. This affects nsXPCComponents_Utils::EvalInSandbox (ie Components.utils.evalInSandbox), throwing NS_ERROR_ILLEGAL_VALUE when passing 1.85 as the desired JS version for the sandbox. Greasemonkey attempts to do this, after determining that 1.85 is the highest JS version, and is therefore broken on trunk.
Assignee: general → nobody
The plan is to remove js-versions completely, so there's no longer any need to map "1.85" to JSVERSION_ECMA_5.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.