Details
-
Sub-task
-
Resolution: Done
-
P3: Somewhat important
-
None
-
None
Description
This is to stay ECMA-compliant, IIRC.
Suggested action: Ensure it's really an ECMA violation and not just a quirk of the old parser. Check if JSEvaluateScript has the same issue. If so, create an upstream bug. Discuss there what the right fix is.