js/src/jit-test/tests/debug/Frame-evalWithBindings-13.js@129ffea94266
js/src/jit-test/tests/debug/Frame-evalWithBindings-13.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 // evalWithBindings correctly handles optional lineNumber option
2 var g = newGlobal();
3 var dbg = new Debugger(g);
4 var count = 0;
6 function testLineNumber (options, expected) {
7 count++;
8 dbg.onDebuggerStatement = function (frame) {
9 dbg.onNewScript = function (script) {
10 dbg.onNewScript = undefined;
11 assertEq(script.startLine, expected);
12 count--;
13 };
14 frame.evalWithBindings("", {}, options);
15 };
16 g.eval("debugger;");
17 }
20 testLineNumber(undefined, 1);
21 testLineNumber({}, 1);
22 testLineNumber({ lineNumber: undefined }, 1);
23 testLineNumber({ lineNumber: 5 }, 5);
24 assertEq(count, 0);
