| browser.js |
|
0 |
- |
| regress-77578-001.js |
Date: 2001-07-11
SUMMARY: Testing eval scope inside a function.
See http://bugzilla.mozilla.org/show_bug.cgi?id=77578
|
2638 |
- |
| regress-154693.js |
Date: 26 Nov 2002
SUMMARY: Testing scope
See http://bugzilla.mozilla.org/show_bug.cgi?id=154693
|
1251 |
- |
| regress-181834.js |
Date: 25 November 2002
SUMMARY: Testing scope
See http://bugzilla.mozilla.org/show_bug.cgi?id=181834
This bug only bit in Rhino interpreted mode, when the
'compile functions with dynamic scope' feature was set.
|
2792 |
- |
| regress-184107.js |
Date: 09 December 2002
SUMMARY: with(...) { function f ...} should set f in the global scope
See http://bugzilla.mozilla.org/show_bug.cgi?id=184107
In fact, any variable defined in a with-block should be created
in global scope, i.e. should be a property of the global object.
The with-block syntax allows existing local variables to be SET,
but does not allow new local variables to be CREATED.
See http://bugzilla.mozilla.org/show_bug.cgi?id=159849#c11
|
1942 |
- |
| regress-185485.js |
Date: 16 Dec 2002
SUMMARY: Testing |with (x) {function f() {}}| when |x.f| already exists
See http://bugzilla.mozilla.org/show_bug.cgi?id=185485
The idea is this: if |x| does not already have a property named |f|,
a |with| statement cannot be used to define one. See, for example,
http://bugzilla.mozilla.org/show_bug.cgi?id=159849#c11
http://bugzilla.mozilla.org/show_bug.cgi?id=184107
However, if |x| already has a property |f|, a |with| statement can be
used to modify the value it contains:
with (x) {f = 1;}
This should work even if we use a |var| statement, like this:
with (x) {var f = 1;}
However, it should NOT work if we use a |function| statement, like this:
with (x) {function f() {}}
Instead, this should newly define a function f in global scope.
See http://bugzilla.mozilla.org/show_bug.cgi?id=185485
|
2826 |
- |
| regress-191276.js |
Date: 30 January 2003
SUMMARY: Testing |this[name]| via Function.prototype.call(), apply()
See http://bugzilla.mozilla.org/show_bug.cgi?id=191276
Igor: "This script fails when run in Rhino compiled mode, but passes in
interpreted mode. Note that presence of the never-called |unused_function|
with |f('a')| line is essential; the script works OK without it."
|
1933 |
- |
| regress-192226.js |
Date: 07 February 2003
SUMMARY: Testing a nested function call under |with| or |catch|
See http://bugzilla.mozilla.org/show_bug.cgi?id=192226
|
1516 |
- |
| regress-202678-001.js |
Date: 19 April 2003
SUMMARY: Testing nested function scope capture
See http://bugzilla.mozilla.org/show_bug.cgi?id=202678
|
1784 |
- |
| regress-202678-002.js |
Date: 19 April 2003
SUMMARY: Testing nested function scope capture
See http://bugzilla.mozilla.org/show_bug.cgi?id=202678
|
1806 |
- |
| regress-208496-001.js |
Date: 05 June 2003
SUMMARY: Testing |with (f)| inside the definition of |function f()|
See http://bugzilla.mozilla.org/show_bug.cgi?id=208496
|
2336 |
- |
| regress-208496-002.js |
Date: 05 June 2003
SUMMARY: Testing |with (f)| inside the definition of |function f()|
See http://bugzilla.mozilla.org/show_bug.cgi?id=208496
In this test, we check that static function properties of
of |f| are read correctly from within the |with(f)| block.
|
2504 |
- |
| regress-220362.js |
Date: 27 Sep 2003
SUMMARY: Calling a local function from global scope
See http://bugzilla.mozilla.org/show_bug.cgi?id=220362
|
1545 |
- |
| regress-446026-01.js |
|
1039 |
- |
| regress-446026-02.js |
|
634 |
- |
| scope-002.js |
Date: 2001-07-02
SUMMARY: Testing visibility of outer function from inner function.
|
1816 |
- |
| scope-003.js |
Date: 2001-07-03
SUMMARY: Testing scope with nested functions
From correspondence with Christopher Oliver <coliver@mminternet.com>:
> Running this test with Rhino produces the following exception:
>
> uncaught JavaScript exception: undefined: Cannot find default value for
> object. (line 3)
>
> This is due to a bug in org.mozilla.javascript.NativeCall which doesn't
> implement toString or valueOf or override getDefaultValue.
> However, even after I hacked in an implementation of getDefaultValue in
> NativeCall, Rhino still produces a different result then SpiderMonkey:
>
> [object Call]
> [object Object]
> [object Call]
Note the results should be:
[object global]
[object Object]
[object global]
This is what we are checking for in this testcase -
|
2450 |
- |
| scope-004.js |
Date: 2001-07-16
SUMMARY: Testing visiblity of variables from within a with block.
See http://bugzilla.mozilla.org/show_bug.cgi?id=90325
|
3095 |
- |
| shell.js |
|
0 |
- |