Closed Bug 737764 Opened 12 years ago Closed 9 years ago

arguments.* no longer triggers a strict warning

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86_64
macOS
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: jruderman, Unassigned)

Details

(Keywords: testcase) 

options('strict');
try {
  (function(){if(arguments.*){ }})()
} catch(e){}

js-dbg-64-9ba1a4e7e47c-darwin: reference to undefined property arguments.*
js-dbg-64-e2144e6ee774-darwin: no warning

Is this an intentional change from the patch in bug 733950?  Does it matter?

(I found this while trying to track down bug 737575.)
It was not intentional, NormalArgumentsObject::optimizedGetElem is skipping the normal get-prop path.  I don't think it matters, but I'll let Waldo comment on that.
Assignee: general → nobody
E4X was removed (bug 788293).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.