From 26a029d407be480d791972afb5975cf62c9360a6 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Fri, 19 Apr 2024 02:47:55 +0200 Subject: Adding upstream version 124.0.1. Signed-off-by: Daniel Baumann --- js/src/jit-test/tests/basic/bug786114.js | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 js/src/jit-test/tests/basic/bug786114.js (limited to 'js/src/jit-test/tests/basic/bug786114.js') diff --git a/js/src/jit-test/tests/basic/bug786114.js b/js/src/jit-test/tests/basic/bug786114.js new file mode 100644 index 0000000000..718d0426c6 --- /dev/null +++ b/js/src/jit-test/tests/basic/bug786114.js @@ -0,0 +1,32 @@ +let expected = 'o!o!o!'; +let actual = ''; + +// g is a function that needs an implicit |this| if called within a |with| +// statement. If we fail to provide that implicit |this|, it will append +// "[object global]" instead of "o!". +let o = { + g: function() { actual += this.toString(); }, + toString: function() { return "o!"; } +} + +// g's presence within the |with| is detected by simple tracking of |with|s +// during parsing. +with (o) { + (function() { g(); })(); +} + +// The eval() defeats the tracking of |with| during parsing. Instead, g's +// presence within the |with| is detected by looking at the scopeChain of the +// ParseContext. +with (o) { + eval("(function() { g(); })()"); +} + +// This is like the above case, but the knowledge of the |with| presence must +// be inherited by the inner function. This is the case that was missed in bug +// 786114. +with (o) { + eval("(function() { (function() { g(); })(); })()"); +} + +assertEq(actual, expected); -- cgit v1.2.3