Closed Bug 71190 Opened 25 years ago Closed 25 years ago

arguments.caller not defined

Categories

(Core :: JavaScript Engine, defect)

x86
Linux
defect
Not set
major

Tracking

()

VERIFIED WONTFIX

People

(Reporter: emberson, Assigned: rogerl)

Details

From Bugzilla Helper: User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.14-5.0 i686) BuildID: JavaScript-C 1.5 pre-release 1 1999 10 31 > uname -a Linux olympia.contact.com 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 i686 unknown within a function, the arguments.caller is not defined. the atom is not set in jsfun.c (where as callee is set). Reproducible: Always Steps to Reproduce: 1. > js -f script.js 2. where within a function in script.js one tries to access arguments.caller 3. Actual Results: arguments.caller is undefined Expected Results: should be calling context hard to print a stack trace if one can not get the caller's
In the past, this was deprecated from JavaScript. For example, see: http://developer.netscape.com:80/docs/manuals/js/core/jsref/function.htm Recently - see bug 65683, also bug 68557 - support for function.caller was added back. Also, function.arguments.callee is now supported. We are about to publish (today!) the tarball for JS1.5 pre-release 3, containing these changes. However,function.arguments.caller does not seem to be currently implemented. cc'ing Brendan in case of any misunderstanding on my part. Does this bug raise a valid point?
Summary: standalone javascipt: arguments.caller not defined → arguments.caller not defined
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
Neither arguments.caller nor function.caller is ECMA-standard. arguments.caller is potentially exploitable in security attacks. We aren't going to restore it, IE/JScript does not support it, so I am marking this bug WONTFIX. /be
Status: RESOLVED → VERIFIED
Marking Verified - emberson@contact.com: thank you for this report. Look for the new tarball of JS; and please see the bugs referenced above for more information on this -
You need to log in before you can comment on or make changes to this bug.