arguments.* no longer triggers a strict warning

RESOLVED WONTFIX

Status

()

Core
JavaScript Engine
--
minor
RESOLVED WONTFIX
6 years ago
3 years ago

People

(Reporter: Jesse Ruderman, Unassigned)

Tracking

({testcase})

Trunk
x86_64
Mac OS X
testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
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.)

Comment 1

6 years ago
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)

Updated

4 years ago
Assignee: general → nobody
E4X was removed (bug 788293).
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.