js/src/jit-test/tests/debug/onDebuggerStatement-02.js@129ffea94266
js/src/jit-test/tests/debug/onDebuggerStatement-02.js
Sat, 03 Jan 2015 20:18:00 +0100
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Sat, 03 Jan 2015 20:18:00 +0100
- branch
- TOR_BUG_3246
- changeset 7
- 129ffea94266
- permissions
- -rw-r--r--
Conditionally enable double key logic according to:
private browsing mode or privacy.thirdparty.isolate preference and
implement in GetCookieStringCommon and FindCookie where it counts...
With some reservations of how to convince FindCookie users to test
condition and pass a nullptr when disabling double key logic.
1 // Activity in the debugger compartment should not trigger debug hooks.
3 var g = newGlobal();
4 var hit = false;
6 var dbg = Debugger(g);
7 dbg.onDebuggerStatement = function (stack) { hit = true; };
9 debugger;
10 assertEq(hit, false, "raw debugger statement in debugger compartment should not hit");
12 g.f = function () { debugger; };
13 g.eval("f();");
14 assertEq(hit, false, "debugger statement in debugger compartment function should not hit");
16 g.outerEval = eval;
17 g.eval("outerEval('debugger;');");
18 assertEq(hit, false, "debugger statement in debugger compartment eval code should not hit");
20 var g2 = newGlobal();
21 g2.eval("debugger;");
22 assertEq(hit, false, "debugger statement in unrelated non-debuggee compartment should not hit");
