Name Description Size Coverage
10.1.6-01.js 627 -
10.1.6.js 598 -
bound-prototype.js 1259 -
browser.js 0 -
construct-bound-proxy-with-many-arguments.js 478 -
delete-arguments.js 3047 -
Function-arguments-gc.js BEGIN TEST * ************ 956 -
get-function-realm.js 1465 -
length-with-destructuring-and-parameter-expression.js 1217 -
Object-toSource.js 10635 -
regress-49286.js Date: 2001-07-10 SUMMARY: Invoking try...catch through Function.call See http://bugzilla.mozilla.org/show_bug.cgi?id=49286 1) Define a function with a try...catch block in it 2) Invoke the function via the call method of Function 3) Pass bad syntax to the try...catch block 4) We should catch the error! 2038 -
regress-58274.js Date: 15 July 2002 SUMMARY: Testing functions with double-byte names See http://bugzilla.mozilla.org/show_bug.cgi?id=58274 Here is a sample of the problem: js> function f\u02B1 () {} js> f\u02B1.toSource(); function f¦() {} js> f\u02B1.toSource().toSource(); (new String("function f\xB1() {}")) See how the high-byte information (the 02) has been lost? The same thing was happening with the toString() method: js> f\u02B1.toString(); function f¦() { } js> f\u02B1.toString().toSource(); (new String("\nfunction f\xB1() {\n}\n")) 4829 -
regress-85880.js Date: 2001-06-14 SUMMARY: Regression test for Bugzilla bug 85880 Rhino interpreted mode was nulling out the arguments object of a function if it happened to call another function inside its body. See http://bugzilla.mozilla.org/show_bug.cgi?id=85880 2467 -
regress-94506.js Date: 08 August 2001 SUMMARY: When we invoke a function, the arguments object should take a back seat to any local identifier named "arguments". See http://bugzilla.mozilla.org/show_bug.cgi?id=94506 2457 -
regress-97921.js Date: 10 September 2001 SUMMARY: Testing with() statement with nested functions See http://bugzilla.mozilla.org/show_bug.cgi?id=97921 Brendan: "The bug is peculiar to functions that have formal parameters, but that are called with fewer actual arguments than the declared number of formal parameters." 2551 -
regress-123371.js 576 -
regress-131964.js Date: 19 Mar 2002 SUMMARY: Function declarations in global or function scope are {DontDelete}. Function declarations in eval scope are not {DontDelete}. See http://bugzilla.mozilla.org/show_bug.cgi?id=131964 2515 -
regress-137181.js Date: 12 Apr 2002 SUMMARY: delete arguments[i] should break connection to local reference See http://bugzilla.mozilla.org/show_bug.cgi?id=137181 1544 -
regress-178389.js 680 -
regress-193555.js Date: 17 February 2003 SUMMARY: Testing access to function name from inside function See http://bugzilla.mozilla.org/show_bug.cgi?id=193555 2182 -
regress-222029-001.js Date: 13 Oct 2003 SUMMARY: Make our f.caller property match IE's wrt f.apply and f.call See http://bugzilla.mozilla.org/show_bug.cgi?id=222029 Below, when gg calls f via |f.call|, we have this call chain: calls calls gg() ---------> Function.prototype.call() ---------> f() The question this bug addresses is, "What should we say |f.caller| is?" Before this fix, SpiderMonkey said it was |Function.prototype.call|. After this fix, SpiderMonkey emulates IE and says |gg| instead. 2347 -
regress-222029-002.js Date: 13 Oct 2003 SUMMARY: Make our f.caller property match IE's wrt f.apply and f.call See http://bugzilla.mozilla.org/show_bug.cgi?id=222029 Below, when gg calls f via |f.call|, we have this call chain: calls calls gg() ---------> Function.prototype.call() ---------> f() The question this bug addresses is, "What should we say |f.caller| is?" Before this fix, SpiderMonkey said it was |Function.prototype.call|. After this fix, SpiderMonkey emulates IE and says |gg| instead. 2549 -
regress-292215.js 804 -
regress-313570.js 767 -
regress-338121-01.js 940 -
regress-338121-02.js 939 -
regress-344052.js 771 -
regress-364023.js 999 -
shell.js 0 -